DO NOT REPLY [Bug 9019] New: - ClassNotFoundException when starting remote server

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9019>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9019

ClassNotFoundException when starting remote server

           Summary: ClassNotFoundException when starting remote server
           Product: JMeter
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: ssadedin@elogex.com


On some JVM's/JDK's starting the remote jmeter engine (using 
org.apache.jmeter.engine.RemoteJMeterEngineImpl) results in a 
ClassNotFoundException in the rmiregistry.  The error appears as

java.rmi.ServerException: Server RemoteException; nested exception is:
        java.rmi.UnmarshalException: error unmarshalling arguments; nested 
exception is:
        java.lang.ClassNotFoundException: 
org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
        java.lang.ClassNotFoundException: 
org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub
java.lang.ClassNotFoundException: 
org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub
        at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer
(StreamRemoteCall.java:245)
        at sun.rmi.transport.StreamRemoteCall.executeCall
(StreamRemoteCall.java:220)
        at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:354)
        at sun.rmi.registry.RegistryImpl_Stub.rebind(Unknown Source)
        at java.rmi.Naming.rebind(Naming.java:160)
        at org.apache.jmeter.engine.RemoteJMeterEngineImpl.main
(C:/programs/jakarta-
jmeter/src/org/apache/jmeter/engine/RemoteJMeterEngineImpl.java:144)

This is happening because of the use of the "ThreadGroup" class which is 
pulling in java.lang.Thread group in some places instead of the correct 
org.apache.jmeter.threads.ThreadGroup.  To avoid this, references to 
org.apache.jmeter.threads.ThreadGroup should be explicitly qualified with the 
full package name in the remote interface and implementation for the 
RemoteJMeterEngine.

A patch will be attached which corrects the error on the submitter's system.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>