I will ask the people responsible for the Tomcat-server, but I don't think
that is the issue.
I looked a bit deeper in the log-file now and found another stack trace that
is thrown before my original stacktrace:
2016-08-10 11:00:57,195 ERROR [geotools.jdbc] - There's code using JDBC
based
: benjoh [mailto:benny...@gmail.com]
Sendt: 10. august 2016 10:02
Til: geoserver-users@lists.sourceforge.net
Emne: Re: [Geoserver-users] Problem reading features: SQLException: Could not
obtain native oracle connection for class com.sun.proxy.$Proxy11
Thanks for the reply!
I am not in control over
Thanks for the reply!
I am not in control over the Tomcat-server we use. I can only deploy
applications and configure them. This is my connection resource if it helps:
These are the jars that are inside tomcat libs: catalina-jmx-remote.jar,
ojdbc7.jar, ons.jar, simplefan.jar,
Hi,
I'm not familiar with the particular error (specifically, the involvement
of a com.sun.Proxy in it), but wondering if you may have the oracle driver
in two
different places at the same time, like in geoserver, but also inside the
tomcat libs?
This might be relevant:
No one has encountered this issue? I am tearing my hair out. Can it have
something to do with the ojdbc.jar or something?
--
View this message in context:
Hi,
I am trying to install GeoServer on a Tomcat-server and I am running into
some trouble.
This is the StackTrace I find in the logs:
java.lang.RuntimeException: Error getting FeatureType, this should never
happen!
at
