Problem w cfqueryparam cfsqltype after upgrade to Java 11

#1

Lucee/CF errors pointing to: javax/xml/bind/DatatypeConverter and actual log below references not finding Instrumentation instance. I was running a few version old version of Lucee, upgraded it to latest stable. Was running fine with the included Java (8). Then upgraded java using Adopt to Java 11. I am thinking maybe I need to locate tools.jar that is referenced and either get it into path or copy it into the JDK as maybe it is not included? But also read this method was to be deprecated in Java 9 so I am not sure. Anyone else experience this? Log snippet below. (Windows 2019 server / IIS / Lucee stable latest version). Tomcat 8.5.xx (latest as of 2 days ago in the 8.5 series don’t recall suffix). Thank you.

INFO",“ajp-nio-8009-exec-4”,“03/28/2019”,“22:56:44”,“Instrumentation”,“not found [lucee.runtime.instrumentation.ExternalAgent] in ClassLoader [jdk.internal.loader.ClassLoaders$AppClassLoader@2f7a2457]”
“INFO”,“ajp-nio-8009-exec-4”,“03/28/2019”,“22:56:44”,“Instrumentation”,“not found [lucee.runtime.instrumentation.ExternalAgent] in ClassLoader [java.net.URLClassLoader@66480dd7]”
“INFO”,“ajp-nio-8009-exec-4”,“03/28/2019”,“22:56:44”,“Instrumentation”,“not found [lucee.runtime.instrumentation.ExternalAgent] in ClassLoader [lucee.commons.io.res.util.ResourceClassLoader@27ce651a]”
“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“not found [lucee.runtime.instrumentation.ExternalAgent] in ClassLoader [sun.misc.Launcher$AppClassLoader@764c12b6]”
“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“not found [lucee.runtime.instrumentation.ExternalAgent] in ClassLoader [java.net.URLClassLoader@33c7353a]”
“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“not found [lucee.runtime.instrumentation.ExternalAgent] in ClassLoader [lucee.commons.io.res.util.ResourceClassLoader@16ea67c0]”
“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“looking for tools.jar”
“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“couldn’t find tools.jar at: D:\lucee\jdk\jre\lib\tools.jar”
“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“tools.jar used:D:\lucee\jdk\lib\tools.jar”
“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“loaded VirtualMachine class:com.sun.tools.attach.VirtualMachine”
“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“try to load agent (path:D:\lucee\tomcat\lucee-server\context\lucee-external-agent.jar)”
“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“pid:1528”
“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“found [lucee.runtime.instrumentation.ExternalAgent] in ClassLoader [sun.misc.Launcher$AppClassLoader@764c12b6]”
“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“ExternalAgent does contain a Instrumentation instance”

0 Likes

#2

I tihnk you are correct because of this…

“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“couldn’t find tools.jar at: D:\lucee\jdk\jre\lib\tools.jar”“INFO”,“ajp-nio-8009-exec-10”,“03/28/2019”,“23:06:12”,“Instrumentation”,“couldn’t find tools.jar at: D:\lucee\jdk\jre\lib\tools.jar”

To get it to work now with the java you have it wants to find that jar at the location specified. I have experienced odd behaviors after performing upgrades. ALWAYS backup your entire Lucee directory before doing upgrades in case you need to fall back. (Although I do believe your version of Lucee includes an automatic fallback mechanism.)

0 Likes