Make sure that your personal code also is the same on both sides..
In the case where you export a jar file your self, you have to have the same
version of the class on both clientside and serverside.. Not sure if this is
relevant in your case though..
On Sun, Dec 7, 2008 at 12:15 PM, Jordi Souchei
The client and the producer are running from the same computer and they are
using the same jar (Activemq-5.3-snapshot.jar).
I've used activemq-5.1 and the last snapshot of activemq-5.3 with the same
results
2008/12/7 Mark Webb <[EMAIL PROTECTED]>
> I saw that once and it was a deserialization pro
I saw that once and it was a deserialization problem. I fixed it by
placing the same set of jar files on both sender and receiver. The
issue was that ActiveMQ was swallowing a ClassNotFoundException and
re-throwing it as a JMSException. I only found it by stepping through
the code in a debugger.
