On 9/10/19 6:17 AM, Humphries, Graham wrote:
Yes I did. I use JNDI data source defined in the Tomcat context.xml
and I have the ojdbc8.jar for Oracle 12c as the driver.
Here is an extract from the Catalina.log when I installed Geosever:
04-Sep-2019 09:09:44.799 SEVERE [localhost-startStop-1]
org.apache.catalina.startup.ContextConfig.processAnnotationsJar Unable
to process Jar entry [module-info.class] from Jar
[file:/opt/tomcat/webapps/geoserver/WEB-INF/lib/txw2-2.4.0-b180830.0438.jar]
for annotations
org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid
byte tag in constant pool: 19
at
org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:97)
at
org.apache.tomcat.util.bcel.classfile.ConstantPool.<init>(ConstantPool.java:54)
at
org.apache.tomcat.util.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:174)
at
org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:83)
at
org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2042)
at
org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1989)
at
org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1959)
at
org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1912)
at
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1154)
at
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:771)
at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:298)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5076)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:952)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1823)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
these error will go away when you use an up-2-date version of tomcat
(any recent 8.5.x not your 2016 version which comes with an incompatible
version of the bcel library); they are caused by tomcat scanning the
jars for TLB files and other annotations; nothing to worry about (you
can configure tomcat to prevent scanning all the jars at the cost of a
request-time performance penalty) but annoying messages filling up the
logs hiding possibly useful information.
Some jars in geoserver have java 11 metadata for upward compatibility.
-M
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
