Sorry, my bad. Was doing testing wrong way.
I have corrected it and works fine.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Here is the source of that class in 5.11.1:
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.activemq/activemq-all/5.11.1/org/apache/activemq/util/ClassLoadingAwareObjectInputStream.java?av=f
If you look at line 112 (the one from your stack trace), you can see that
it doesn't log the err
Clients are running on older version : < 5.11.1
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
What specific version of 5.11 is your client running? The security fix that
added this check (https://issues.apache.org/jira/browse/AMQ-6013) was
back-ported to 5.11.3, so if you're using that version of 5.11 or later,
then you have that change.
Tim
On Tue, Sep 12, 2017 at 12:19 AM, khandelwalanu
Hi,
Currently ActiveMQ broker is using ActiveMQ v5.14 while clients are still
running on v5.11. In the client migration process, we are facing below
problem with ObjectMessages:
The cases when producer is migrated to 5.14 but consumer is still using the
older version(5.11) are failing and throwi
Hi,
Currently ActiveMQ broker is using ActiveMQ v5.14 while clients are still
running on v5.11. In the client migration process, we are facing below
problem with ObjectMessages:
The cases when producer is migrated to 5.14 but consumer is still using the
older version(5.11) are failing and throwi
