0 Replies Latest reply on Dec 27, 2006 7:05 AM by mskonda

Mismatch version of JBossSerialization signature

mskonda Dec 27, 2006 7:05 AM

Server A is purely an applicaiton server (call it as EAI server) without JMS (JBossMessaging) capabilities.

Server B is purely JMS server (with JBossMessage 1.0.1GA) call it as JMS Server.

The EAI server has been started on Dec 21 at 11pm. It connected to JMS server and all is happy.

On 23rd December, the EAI reported an error:

[20061223 02:14:44.357GMT] SEVERE [JDK14LoggerPlugin] [error] [16] Caught exception from connection
java.lang.Exception: Could not connect to server.
 at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:117)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)

[20061223 02:14:44.359GMT] WARNING [JDK14LoggerPlugin] [warn] [16] JMS provider failure detected:
javax.jms.JMSException: Throwable received from underlying connection
 at org.jboss.jms.client.container.ConnectionAspect.handleConnectionException(ConnectionAspect.java:203)
 at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:139)

[20061223 02:14:45.362GMT] SEVERE [JDK14LoggerPlugin] [error] [17] Caught exception from connection
java.lang.Exception: Could not connect to server.
 at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:117)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)

At the same time, JMS Server reported error too:

[20061223 02:15:21.843GMT] WARNING [JDK14LoggerPlugin] [warn] [11] A problem has been detected with the connection to remote client a32652m-q2uq3e-ew0lj9yf-1-ew0m566c-16k. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed.
[20061223 02:15:25.435GMT] SEVERE [JDK14LoggerPlugin] [error] [12] Failed to accept socket connection
java.lang.reflect.InvocationTargetException
 at sun.reflect.GeneratedConstructorAccessor35.newInstance(Unknown Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
 at org.jboss.remoting.transport.socket.ServerThread.createServerSocket(ServerThread.java:202)
 at org.jboss.remoting.transport.socket.ServerThread.wakeup(ServerThread.java:243)
 at org.jboss.remoting.transport.socket.SocketServerInvoker.processInvocation(SocketServerInvoker.java:535)
 at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:450)
 at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.SocketException: Connection reset
 at java.net.SocketInputStream.read(SocketInputStream.java:168)
 at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
 at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
 at java.io.FilterInputStream.read(FilterInputStream.java:90)
 at org.jboss.serial.io.JBossObjectInputStream.checkSignature(JBossObjectInputStream.java:110)
 at org.jboss.serial.io.JBossObjectInputStream.<init>(JBossObjectInputStream.java:94)
 at org.jboss.remoting.serialization.impl.jboss.JBossSerializationManager.createInput(JBossSerializationManager.java:59)
 at org.jboss.remoting.transport.socket.ServerSocketWrapper.createInputStream(ServerSocketWrapper.java:56)
 at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:76)
 at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:54)
 at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:50)
 ... 8 more

[20061223 02:15:25.436GMT] SEVERE [JDK14LoggerPlugin] [error] [12] Failed to accept socket connection
java.lang.reflect.InvocationTargetException
 at sun.reflect.GeneratedConstructorAccessor33.newInstance(Unknown Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
 at org.jboss.remoting.transport.socket.ServerThread.createServerSocket(ServerThread.java:202)
 at org.jboss.remoting.transport.socket.ServerThread.wakeup(ServerThread.java:243)
 at org.jboss.remoting.transport.socket.SocketServerInvoker.processInvocation(SocketServerInvoker.java:535)
 at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:450)
 at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.IOException: Mismatch version of JBossSerialization signature
 at org.jboss.serial.io.JBossObjectInputStream.checkSignature(JBossObjectInputStream.java:113)
 at org.jboss.serial.io.JBossObjectInputStream.<init>(JBossObjectInputStream.java:94)
 at org.jboss.remoting.serialization.impl.jboss.JBossSerializationManager.createInput(JBossSerializationManager.java:59)
 at org.jboss.remoting.transport.socket.ServerSocketWrapper.createInputStream(ServerSocketWrapper.java:56)
 at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:76)
 at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:54)
 at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:50)
 ... 8 more

After following the previous threads, I have checked the versions of JBoss Serialisation and Remoting on both the servers and can confirm they are same.
We dont' have a firewall on these boxes and also we have got all permissions to create sockets.

This situation only happens when the server is left running overnight or long..

Any clues much appreciated!

Thanks
Madhu