]
Tim Fox closed JBMESSAGING-927.
-------------------------------
Resolution: Duplicate Issue
java.io.IOException:
EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for
deserialization
------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-927
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-927
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Remoting
Affects Versions: 1.2.0.GA
Environment: jboss 4.2.0CR1, java 1.5, jboss messaging 1.2.0ga
Reporter: David
Fix For: Unscheduled
Attachments: dave-jms.tar.bz2
09:58:12,495 ERROR [ServerThread] failed
java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class
invalid for deserialization
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:571)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:479)
at
EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.readObject(ConcurrentHashMap.java:1205)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at org.jboss.jms.wireformat.SerializedPacket.read(SerializedPacket.java:72)
at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:307)
at
org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:641)
at
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:523)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:377)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)
09:58:14,711 WARN [Lease] Tried to terminate lease for session id
5c4o1w13-o9260j-ezjuc4ur-1-ezjuc5w1-4, but no collection of clients have been set.
09:58:14,711 WARN [Lease] Tried to terminate lease for session id null, but no
collection of clients have been set.
That exception can be caused when using the jboss-messaging-client.jar that ships with
the jboss-messaging release. The jboss-messaging-client.jar contains a version of
EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment that implements Serializable.
However, the jboss app server contains a "concurrent.jar" that has a version of
ConcurrentHashMap$Segment that does not implement Serializable. Replacing the version of
lib/concurrent.jar with a version of concurrent.jar that contains a
ConcurrentHashMap$Segment that implements Serializable will solve this issue.
This situation occurs when you have a remote client that sends a message to a Queue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: