I have a script in Together that stops a running JBoss server. The scripts
uses the JMX interface and needs connector.jar, jndi.jar, jmxri.jar and
jnp-client.jar.
If I use the 2.2 versions of these jars everything works as expected and
the server is stopped.
If I use the 2.4 versions of these jars it still stops the server but I get
an exception thrown as shown below. Is this expected behaviour?
Mike S-R
java.rmi.UnmarshalException: Error unmarshaling return header; nested exception
is:
java.net.SocketException: Connection reset by peer: JVM_recv in
socket input stream read
java.net.SocketException: Connection reset by peer: JVM_recv in socket
input stream read
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:86)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
at java.io.BufferedInputStream.read(BufferedInputStream.java:204)
at java.io.DataInputStream.readByte(DataInputStream.java:222)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:186)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
at org.jboss.jmx.server.RMIConnectorImpl_Stub.invoke(Unknown Source)
at
org.jboss.jmx.client.RMIClientConnectorImpl.invoke(RMIClientConnectorImpl.java:485)
at
com.togethersoft.modules.jbosslauncher.JBossStop.run(JBossStop.java:94)
at
com.togethersoft.modules.jbosslauncher.JBossLauncher$2.actionPerformed(JBossLauncher.java:72)
at zcbo.execute([DashoPro-V2-050200])
at zaoa.run([DashoPro-V2-050200])
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development