Hi Kristian,
On the logging front, that's a great idea; sadly, GeoTools shallows
ClassNotFound exceptions (1) since they can be quite common (and in
many classes are not an critical error).
I tried to come up with a 'short' list of jars from the Cassandra
lib directory which would need to be copied into GeoServer's
WEB-INF/lib directory. It looks like the list would include
*cassandra*, *metrics*, and some subset of the logs, and at least
one more jar which I couldn't identify during my layover.:(
As a quick solution, I can confirm that copying all the jars from
the Cassandra lib directory over to WEB-INF/lib does work. Can you
give that a try?
Cheers,
Jim
1.
https://github.com/geotools/geotools/blob/master/modules/library/metadata/src/main/java/org/geotools/factory/FactoryRegistry.java#L830-L837
On 2/10/2017 9:02 AM, Kristian Nygaard
Jensen wrote:
Here is my current log config
On 2017-02-10 14:36, Kristian Nygaard Jensen wrote:
On 2017-02-09 21:25, Eric Talbot wrote:
Hello Kristian,
We've done all of our testing with Cassandra 3.9. It might be
worth upgrading your cassandra and then trying again. Just
make sure to copy the upgraded Cassandra jars in
geomesa/WEB-INF/lib.
Eric
I have now tried to change the cassandra libs to the official
apache cassandra 3.9, and get the same result. Do you know how
to make geotools logs more verbose?
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/geomesa-users
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/geomesa-users
|
