]
Kevin Conner closed JBESB-494.
------------------------------
Resolution: Rejected
This is not a bug as there are different versions of jboss-messaging being used. These
versions do not interoperate.
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: