Connect JBoss 3.2.5 with JBoss 4.0.3 JMS

[tdevos]

Hi,

All our customers are working with JBoss 3.2.5 on their location. They communicate with each other over JMS. All communication between our customers is forwarded to a central JBoss 3.2.5 server wich validates and forwards the JMS message to another JBoss 3.2.5 server. Until now we had no problems since all servers are JBoss 3.2.5. However, some customers want to update to JBoss 4.0.3. This introduces a problem that the JAR files are not in sync.

Is there a way to connect JBoss 3.2.5 to 4.0.3 and vice versa. The problem is that the beans deployed on the servers are also sending JMS messages so they need to have the right JAR files. Maybe there is some kind "tunneler" which I can run on the central server to forward the JBoss 4.0.3 messages to 3.2.5.

Does anybody have experience connecting 2 different versions of JBoss regarding JMS.

Thanks in advance for replying.

Tim De Vos

[genman]

Although the .jar files are different, the intent is that different versions can talk to each other. The main issue in getting communication to work is having the same serialization (serialization ID) and protocol format.

There may be serialization issues, mainly differences in the serialization ID. I'm not sure what version the serialization ID was established in. I'm thinking 3.2.6.

[tdevos]

Thank you for your reply. The Serialization ID`s are indeed a problem. Since we are using JBoss 3.2.5 there won`t be an option I think.

Regards,

Tim De Vos