Author |
Message
|
tr |
Posted: Sun Apr 13, 2014 8:45 pm Post subject: Incompatible Class Change Error for Tibco EMS 8.0 |
|
|
Novice
Joined: 30 Mar 2014 Posts: 11
|
I am trying to transfer message between 2 Tibco EMS queues using 2 JMS nodes. I am using the versions Tibco EMS 8.0 amd IIB. Even though the message is delivered to the output queue, my flow is getting time out saying that the output monitor emcountered an error while getting the message. java.lang.IncompatibleClassChange Error. I am using the test client in broker to test the flow.
I am able to achieve the same using Java code. Is there any bad version of jar files along with Tibco EMS 8.0 which is not compatible with other jar files? |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Apr 13, 2014 10:45 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20763 Location: LI,NY
|
If you are mixing 2 JMS providers in your flow (bridge scenario) the broker might have difficulty picking the right implementation for javax.jms.Message class...
Did you think about using distinct flows/ subflows with distinct classloaders?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
tr |
Posted: Mon Apr 14, 2014 3:17 am Post subject: |
|
|
Novice
Joined: 30 Mar 2014 Posts: 11
|
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Apr 14, 2014 4:16 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20763 Location: LI,NY
|
Thanks for the URL but that page is not available for me...
Have you checked which JMS implementation was chosen? May be you do need a class loader configurable service.... My guess is it still has to do with some confusion as to the implementation class of the javax.jms.Message class.
Try not using the test client but using Tibco to place and read the test messages.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
tr |
Posted: Wed Apr 16, 2014 2:47 am Post subject: |
|
|
Novice
Joined: 30 Mar 2014 Posts: 11
|
|
Back to top |
|
 |
|