activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <christian.po...@gmail.com>
Subject Re: Exception in thread "ActiveMQ Transport: tcp:///10.80.0.35:38499" java.lang.ClassCastException: org.apache.activemq.command.ReplayCommand
Date Fri, 12 Apr 2013 14:00:13 GMT
Well, that's a surprisingly old version :)
But what's happening is the broker is expecting a ConnectionInfo object off
the wire, and when it either pulls it from the cache or reads it off the
wire, it's not getting the correct type of object it desires (ConnectionId).

Are any of your clients using 1) newer versions of the activemq client, or
2) udp protocol?

There are different versions of the openwire protocol (9 being the current,
looks like 1 is what's being used on your end) and they should be backward
compatible. You're probably better off upgrading to a later version as I
don't see anyone having this same issue with the latest releases.

HTH

Christian




On Fri, Apr 12, 2013 at 3:57 AM, mmg <manjusha.gole@gmail.com> wrote:

> We are using pretty old version of Active MQ. Its 4.0.1 :-(. We are
> planning
> to upgrade to latest one. But before that want to know what causes this
> exception and also if upgrading to latest version of Active MQ will resolve
> this issue.
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Exception-in-thread-ActiveMQ-Transport-tcp-10-80-0-35-38499-java-lang-ClassCastException-org-apache-d-tp4665770p4665887.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message