The reason they can't talk is due to the serialization differences, but these have been fixed in later versions.
Upgrade 3.2.3 to a newer version (3.2.7) with serialization compatibility.
If you can't do a full upgrade, then it's probably a pretty complicated job. You may be able to create your own 3.2.3 with the serialization fixes from a later release.
I cannot upgrade due to these are production systems.
What i am trying to do is to add a bridge between these two system to parse the JMS message and then create new JMS messages.
Now, the coming problem is the classloader issue because i need to use two different version of jbossmq-client in the same bridge JVM.
Of course, i can build the bridge by using two JVM communicated through network. But i would like to try one JVM first because one JVM gives more reliability.
If the serialization is different between versions, you can't really do what you describe without changing the underlying bytes in the message, namely changing the Serialization ID to match.