Unfortunately our environment has a number of JMS clients talking to a 3.2.3
JMS server. We had planned to update SOME of the the JMS clients to 3.2.6 when
we experienced this class compatibility problem.
My question is can we RELIABLY backport the MQ version in 3.2.3 to the 3.2.6
version? I
I would just overlay the class (MapMessage) itself from 3.2.3 in the 3.2.6
classfile. This would probably the most trouble free. Your milage may vary,
however.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3871806#3871806
Reply to the post :
The jms MapMessage implementation changed between 3.2.3 and 3.2.6 such that its
not serializable compatible, but the serialVersionUID was not changed.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857225#3857225
Reply to the post :
I get a ClassCastException when attempting to send a MapMessage to a queue.
I'm running JBoss 4.0.0. The same code worked in JBoss 3.2.3.
| MapMessage message = queueSession.createMapMessage();
| for (Iterator iter = messageData.keySet().iterator(); iter.hasNext();)
| {
|
Apparently, the MapMessage is not compatible with different versions of JBoss.
The ClassCastException occurred when sending a MapMessage from JBoss 4.0.0
server to JBoss 3.2.3 server. The error does not occur when sending a
MapMessage among JBoss 4.0.0 servers.
View the original post :
Probably versions 3.2.6+ and 4.0 are serializable compatible.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3856979#3856979
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3856979
Anyone? Ideas?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3852965#3852965
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3852965
---
This SF.Net email is sponsored by:
