[
http://jira.jboss.com/jira/browse/JBESB-494?page=comments#action_12358003 ]
Kevin Conner commented on JBESB-494:
------------------------------------
The mismatch is *not* due to patched jars but is due to different versions of
jboss-messaging.
Running a 1.2.0GA client, patched or otherwise, against a 1.0.1SP4 server will not work.
Please note that the messaging team have recently release 1.2.0sp1. If you choose to
install this version then you should update the client jars within ESB so that they match
(just in case there are other differences from 1.2.0GA).
Version mismatch between ESB 4.2MR1 - and JBoss Messaging server
----------------------------------------------------------------
Key: JBESB-494
URL:
http://jira.jboss.com/jira/browse/JBESB-494
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 1
Environment: jbossesb-4.2 (from src: jbossesb-4.2MR1-src.zip)
jboss-4.0.5.GA (from src: jboss-4.0.5.GA-src.tar.gz)
JBoss Messaging server (jboss-messaging-1.0.1.SP4-src)
Sun Java 1.5
RHEL5
Reporter: Len DiMaggio
Assigned To: Mark Little
This JIRA tracks the issue raised in ESB user forum:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033350#...
According to Kurt, the versionID mismatch is due to patched jar files. This JIRA is thin
on details - Kurt, can you elaborate? Thanks!
runtest:
[echo] Runs Test JMS Sender
[java] Exception in thread "main" javax.naming.CommunicationException
[Root exception is java.io.InvalidClassException:
org.jboss.jms.client.delegate.DelegateSupport; local class incompatible: stream classdesc
serialVersionUID = 8005108339439737469, local class serialVersionUID =
-1723908125830723356]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira