Upgrade of jdk / jre to java 8 lucee failed

tapirus · February 25, 2018, 12:48pm

Hi,
I tried to upgrade my jdk / jre to java 8 on lucee.

I followed this instruction
http://docs.lucee.org/guides/Various/installation-installer-documentation/installation-windows/upgrade-JRE.html

Server is Windows 2008 R2 and lucee 5.2.5.20. (upgraded a long time ago from railo).

I copied the files of the jdk folder
to C:\railo\jdk
and have the path
C:\railo\jdk\bin\server\jvm.dll
in the Tomcat administrator
I

The tomcat administrator says tomcat is started.
But no web pages are being served.

What did I miss?
Regards
Thorsten

Zackster · February 25, 2018, 10:10pm

have a look at the log files?

tapirus · February 26, 2018, 8:30am

In which log file I have to look for this issue?
catalina.log?

There is something like:

Feb 24, 2018 7:55:42 PM org.apache.catalina.startup.Catalina start
INFORMATION: Server startup in 30001 ms
Feb 24, 2018 8:03:30 PM org.apache.coyote.AbstractProtocol pause
INFORMATION: Pausing ProtocolHandler ["http-bio-8888"]
Feb 24, 2018 8:03:30 PM org.apache.coyote.AbstractProtocol pause
INFORMATION: Pausing ProtocolHandler ["ajp-bio-8009"]
Feb 24, 2018 8:03:30 PM org.apache.catalina.core.StandardService stopInternal
INFORMATION: Stopping service Catalina
Feb 24, 2018 8:03:31 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SCHWERWIEGEND: The web application [/host-manager] appears to have started a thread named [FelixDispatchQueue] but has failed to stop it. This is very likely to create a memory leak.
Feb 24, 2018 8:03:31 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SCHWERWIEGEND: The web application [/host-manager] appears to have started a thread named [FelixFrameworkWiring] but has failed to stop it. This is very likely to create a memory leak.
Feb 24, 2018 8:03:31 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SCHWERWIEGEND: The web application [/host-manager] appears to have started a thread named [FelixStartLevel] but has failed to stop it. This is very likely to create a memory leak.
Feb 24, 2018 8:03:31 PM org.apache.catalina.core.StandardContext listenerStop
SCHWERWIEGEND: Exception sending context destroyed event to listener instance of class com.nr.agent.instrumentation.tomcat7.TomcatServletRequestListener
java.lang.NullPointerException
	at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:4794)
	at org.apache.catalina.core.StandardContext$4.run(StandardContext.java:5473)
	at java.lang.Thread.run(Unknown Source)

Feb 24, 2018 8:05:42 PM org.apache.catalina.core.AprLifecycleListener init
INFORMATION: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\railo\tomcat\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files\nodejs\;;.
Feb 24, 2018 8:05:47 PM org.apache.coyote.AbstractProtocol init
INFORMATION: Initializing ProtocolHandler ["http-bio-8888"]
Feb 24, 2018 8:05:47 PM org.apache.coyote.AbstractProtocol init
INFORMATION: Initializing ProtocolHandler ["ajp-bio-8009"]
Feb 24, 2018 8:05:47 PM org.apache.catalina.startup.Catalina load
INFORMATION: Initialization processed in 10868 ms
Feb 24, 2018 8:05:47 PM org.apache.catalina.core.StandardService startInternal
INFORMATION: Starting service Catalina
Feb 24, 2018 8:05:47 PM org.apache.catalina.core.StandardEngine startInternal
INFORMATION: Starting Servlet Engine: Apache Tomcat/7.0.22
Feb 24, 2018 8:05:47 PM org.apache.catalina.startup.HostConfig deployDirectory
INFORMATION: Deploying web application directory host-manager
Feb 24, 2018 8:06:14 PM org.apache.catalina.startup.HostConfig deployDirectory
INFORMATION: Deploying web application directory ROOT
Feb 24, 2018 8:06:17 PM org.apache.catalina.startup.HostConfig deployDirectory
INFORMATION: Deploying web application directory tomcat-docs
Feb 24, 2018 8:06:18 PM org.apache.catalina.startup.HostConfig deployDirectory
INFORMATION: Deploying web application directory tomcat-manager
Feb 24, 2018 8:06:21 PM org.apache.catalina.startup.Catalina start
SCHWERWIEGEND: Catalina.start: 
org.apache.catalina.LifecycleException: Failed to start component [StandardServer[8005]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:621)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:450)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardService[Catalina]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
	at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:727)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:148)
	... 7 more
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
	at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:148)
	... 9 more
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[schematherapie-bonn.de]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1033)
	at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:291)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:148)
	... 11 more
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[schematherapie-bonn.de].StandardContext[]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1033)
	at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:774)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:148)
	... 14 more
Caused by: org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 18
	at org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:131)
	at org.apache.tomcat.util.bcel.classfile.ConstantPool.<init>(ConstantPool.java:60)
	at org.apache.tomcat.util.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:209)
	at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:119)
	at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:1967)
	at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1858)
	at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1826)
	at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1812)
	at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1306)
	at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:896)
	at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:322)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
	at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5103)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:148)
	... 17 more

Feb 24, 2018 8:06:21 PM org.apache.catalina.startup.Catalina start
INFORMATION: Server startup in 34703 ms

Zackster · February 26, 2018, 12:44pm

Dunno what the exact problem is but Tomcat 7 is pretty old, I’d suggest doing a clean install via the windows installer?

kabutotx · February 26, 2018, 8:41pm

Get the latest installer or at least try the latest Tomcat 7. 7.0.22 is way old and has security holes.

modius · February 28, 2018, 1:39am

Yikes 7.0.22 is 7+ years old.

Zackster · February 28, 2018, 1:56am

what do you think about adding a version check and warning for old/insecure versions of tomcat in the admin server overview? given it’s bundled with lucee?

I updated the http://docs.lucee.org/guides/Various/installation-installer-documentation/installation-windows/upgrade-JRE.html page with the following advice about upgrading tomcat yesterday

Keep in mind that your Tomcat software also needs to be updated for security and performance fixes. The easiest way to achieve this is a fresh install of Lucee using the latest Lucee Installer which will install and configure the latest versions of Lucee, JRE and Tomcat.

kabutotx · February 28, 2018, 5:12am

Might want to mention the link for Tomcat security reports.
http://tomcat.apache.org/security.html
The main page doesn’t always list CVEs fixed.