Zorka Jetty 9.3 Compatibility Issues

21 visualitzacions
Ves al primer missatge no llegit

John King

no llegida,
28 de set. 2016, 14:41:5728/9/16
a Zorka Users
I'm trying to get http metrics from a jetty 9.3 server using eclipse/jetty.bsh. Turning on trace logging I get the following error:

2016-09-20 08:42:04 DEBUG SpyClassTransformer Error Transforming class: org/eclipse/jetty/servlet/ServletHandler [java.lang.RuntimeException: java.lang.ClassNotFoundException: org/eclipse/jetty/server/handler/ContextHandler$StaticContext]
java.lang.RuntimeException: java.lang.ClassNotFoundException: org/eclipse/jetty/server/handler/ContextHandler$StaticContext
	at com.jitlogic.zorka.deps.asm.ClassWriter.getCommonSuperClass(Unknown Source)
	at com.jitlogic.zorka.deps.asm.ClassWriter.a(Unknown Source)
	at com.jitlogic.zorka.deps.asm.Frame.a(Unknown Source)
	at com.jitlogic.zorka.deps.asm.Frame.a(Unknown Source)
	at com.jitlogic.zorka.deps.asm.MethodWriter.visitMaxs(Unknown Source)
	at com.jitlogic.zorka.deps.asm.ClassReader.a(Unknown Source)
	at com.jitlogic.zorka.deps.asm.ClassReader.b(Unknown Source)
	at com.jitlogic.zorka.deps.asm.ClassReader.accept(Unknown Source)
	at com.jitlogic.zorka.deps.asm.ClassReader.accept(Unknown Source)
	at com.jitlogic.zorka.core.spy.SpyClassTransformer.transform(SpyClassTransformer.java:305)
	at sun.instrument.TransformerManager.transform(TransformerManager.java:188)
	at sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:428)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:455)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:367)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at org.eclipse.jetty.webapp.Configuration$ClassList.<init>(Configuration.java:148)
	at org.eclipse.jetty.webapp.Configuration$ClassList.serverDefault(Configuration.java:143)
	at org.eclipse.jetty.webapp.Configuration$ClassList.setServerDefault(Configuration.java:115)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at org.eclipse.jetty.util.TypeUtil.call(TypeUtil.java:523)
	at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.call(XmlConfiguration.java:726)
	at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:417)
	at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:358)
	at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:259)
	at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1498)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1435)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at org.eclipse.jetty.start.Main.invokeMain(Main.java:214)
	at org.eclipse.jetty.start.Main.start(Main.java:457) 
at org.eclipse.jetty.start.Main.main(Main.java:75)

At first I thought it was an error with the class writer trying to write an inner class of a class that was currently under construction, but the more I dive into this the more I think it might be a problem with jetty segregating class loaders. Has anyone been able to get jetty 9.3 to work with zorka http stats? Any idea how to resolve this error?

John King

no llegida,
29 de set. 2016, 16:59:3829/9/16
a Zorka Users
I finally figured it out. I just added 
zorka.spy.compute.frames = no
to the zorka.properties and then added the  “-noverify” option to the command line params.
Respon a tots
Respon a l'autor
Reenvia
0 missatges nous