Crash when stopping JbossProfiler 2.0.Beta 1

[pisce]

Hello,

I'm currently evaluating the JBoss profiler 2.0.Beta 1, and after one successful attempt, I keep getting the folowing error when stopping the profiler:

2008-05-13 15:06:06,866 ERROR [org.jboss.profiler.client.cmd.Client]
java.lang.NullPointerException
at org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:630)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:474)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(CoreReflectionFactory.java:95)
at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:107)
at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:31)
at sun.reflect.annotation.AnnotationParser.parseSig(AnnotationParser.java:370)
at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:181)
at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:69)
at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:52)
at java.lang.Class.initAnnotationsIfNecessary(Class.java:3031)
at java.lang.Class.getDeclaredAnnotations(Class.java:3019)
at org.jboss.profiler.agent.ClassUtil.isSession(ClassUtil.java:152)
at org.jboss.profiler.agent.ClassUtil.getClasses(ClassUtil.java:94)
at org.jboss.profiler.agent.Profiler.stopProfiler(Profiler.java:146)
at org.jboss.profiler.connectors.AbstractHandler.handleCommand(AbstractHandler.java:51)
at org.jboss.profiler.connectors.SocketHandler.invoke(SocketHandler.java:50)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:254)



I followed the readme file for installing and executing the profiler. Any hint/advice/workaround?

[jesper.pedersen]

The server is unable to find the definition of the class - which is strange since the class is passed in as a parameter to the method.

How do you set up your application ? loader-repository and so on

[pisce]

Hi, my loader-repository conf is like this:

<jboss-app>
<loader-repository>
seam.jboss.org:loader=<webapp name>
</loader-repository>
</jboss-app>

application.xml looks like the following:



<web-uri><webapp name>.war</web-uri>
<context-root>/<webapp name></context-root>




<webapp name>.jar



jboss-seam.jar


I don't know if you need some other info, please tell me if you do.

And note that this happens only at the first or second attempt to stop the profiler, otherwise it never happens. When it fails, I can only make it work by restarting JBoss AS.

[pisce]

Seems like I can't edit my post... here's the real application.xml

<display-name>*webapp name*</display-name>

 <module>
 <web>
 <web-uri>*webapp name*.war</web-uri>
 <context-root>/*webapp name*</context-root>
 </web>
 </module>

 <module>
 <ejb>*webapp name*.jar</ejb>
 </module>

 <module>
 <ejb>jboss-seam.jar</ejb>
 </module>

[jesper.pedersen]

Ok - I see.

If you can create a sample archive that fails and create a JIRA issue and attach the file to it we can look into this quicker.

TIA !

[pisce]

Hello,

I think I won't be able to provide such an app, since it occurs very randomly (or so it seems) in my very app...

Anyway, here's something I never noticed before... after one of those crashes, I killed (ctrl+c on Windows) my JBoss AS and got this server-side error:

14:56:23,946 ERROR [STDERR] Exception in thread "Thread-0" (Thread-0)
14:56:23,950 ERROR [STDERR] java.lang.NullPointerException (Thread-0)
14:56:23,958 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:630)
(Thread-0)
14:56:23,963 ERROR [STDERR] at java.lang.ClassLoader.loadClass(ClassLoader.java:306) (Thread-0)
14:56:23,967 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:4
74) (Thread-0)
14:56:23,974 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
(Thread-0)
14:56:23,984 ERROR [STDERR] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) (Thread-0)
14:56:23,988 ERROR [STDERR] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) (Thread-0)
14:56:23,990 ERROR [STDERR] at java.lang.Class.forName0(Native Method) (Thread-0)
14:56:23,993 ERROR [STDERR] at java.lang.Class.forName(Class.java:242) (Thread-0)
14:56:23,998 ERROR [STDERR] at sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(CoreReflectionFactor
y.java:95) (Thread-0)
14:56:24,004 ERROR [STDERR] at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:107) (Threa
d-0)
14:56:24,010 ERROR [STDERR] at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:31) (Thre
ad-0)
14:56:24,016 ERROR [STDERR] at sun.reflect.annotation.AnnotationParser.parseSig(AnnotationParser.java:370) (Thread-0
)
14:56:24,022 ERROR [STDERR] at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:181) (T
hread-0)
14:56:24,028 ERROR [STDERR] at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:69) (
Thread-0)
14:56:24,034 ERROR [STDERR] at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:52) (T
hread-0)
14:56:24,041 ERROR [STDERR] at java.lang.Class.initAnnotationsIfNecessary(Class.java:3031) (Thread-0)
14:56:24,043 ERROR [STDERR] at java.lang.Class.getDeclaredAnnotations(Class.java:3019) (Thread-0)
14:56:24,046 ERROR [STDERR] at org.jboss.profiler.agent.ClassUtil.isSession(ClassUtil.java:152) (Thread-0)
14:56:24,050 ERROR [STDERR] at org.jboss.profiler.agent.ClassUtil.getClasses(ClassUtil.java:94) (Thread-0)
14:56:24,054 ERROR [STDERR] at org.jboss.profiler.agent.Profiler.stopProfiler(Profiler.java:146) (Thread-0)
14:56:24,056 ERROR [STDERR] at org.jboss.profiler.agent.Agent$1.run(Agent.java:918) (Thread-0)

Hope this helps!

[pisce]

For others facing this problem, it seems that a workaround may be to warm-up the profiler by starting/stopping it just after JBoss AS started, without any action done on it.