[jboss-user] [JBoss Messaging] - Re: JMS Exceptions / Mismatch of JBossSerialization version

[rtm333]

I have to partially correct my previous statement. Although we did not observe issue 2) since upgrading to JBM 1.0.1.SP4, issue 1) now reoccurred.

It happened again under Solaris 10 as well as under Redhat Linux.  As imaeses remarked in an earlier posting it seems to be related to heavy (server) load. 

As far as I can tell there two different incarnations of the exception:


  | 2007-04-18 13:22:27,632 ERROR [org.jboss.remoting.transport.socket.ServerThread] Worker thread initialization failure
  | java.lang.reflect.InvocationTargetException
  |     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  |     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
  |     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
  |     at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
  |     at org.jboss.remoting.transport.socket.ServerThread.createServerSocketWrapper(ServerThread.java:694)
  |     at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:358)
  |     at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)
  | 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:57)
  |     at org.jboss.jms.server.remoting.ServerSocketWrapper.createInputStream(ServerSocketWrapper.java:125)
  |     at org.jboss.jms.client.remoting.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:123)
  |     at org.jboss.jms.client.remoting.ClientSocketWrapper.<init>(ClientSocketWrapper.java:73)
  |     at org.jboss.jms.server.remoting.ServerSocketWrapper.<init>(ServerSocketWrapper.java:67)
  |     ... 7 more
  | 

and 


  | 2007-04-18 14:22:33,886 ERROR [org.jboss.remoting.transport.socket.ServerThread] Worker thread initialization failure
  | java.lang.reflect.InvocationTargetException
  |     at sun.reflect.GeneratedConstructorAccessor80.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.createServerSocketWrapper(ServerThread.java:694)
  |     at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:358)
  |     at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)
  | 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:57)
  |     at org.jboss.jms.server.remoting.ServerSocketWrapper.createInputStream(ServerSocketWrapper.java:125)
  |     at org.jboss.jms.client.remoting.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:123)
  |     at org.jboss.jms.client.remoting.ClientSocketWrapper.<init>(ClientSocketWrapper.java:73)
  |     at org.jboss.jms.server.remoting.ServerSocketWrapper.<init>(ServerSocketWrapper.java:67)
  |     ... 6 more
  | 

Besides these exceptions I can detect no actual problems caused by this issue. Nevertheless I find it to some extent worrying.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038449#4038449

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038449