You need to put all relevant JARs onto the broker's classpath, either by
putting them into a folder that will be automatically added to the
classpath (e.g. lib) or by putting them somewhere else and modifying the
start script to add them to the classpath.
Tim
On Mar 30, 2017 4:43 PM, "hyrahul64"
Hi Tim,Thanks for your prompt reply. So what should be done to get rid of
this? How this custom class can be made available to Active MQ(Broker)?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Active-MQ-viewing-messages-in-queue-tp4724326p4724379.html
Sent from the Activ
One common cause of that exception is when you send an ObjectMessage whose
object contains a class that's on the classpath of your producer and your
consumer but not on the classpath of the broker. This could be a custom
class you wrote, or something out of third-party library you depend on.
Tim
