[
https://issues.apache.org/activemq/browse/AMQ-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39970
]
lhotari edited comment on AMQ-1169 at 8/17/07 3:23 AM:
-----------------------------------------------------------
I'm experiencing the same problem on the client side.
Exception in thread "ActiveMQ Transport: tcp://localhost/127.0.0.1:61616"
java.lang.ClassCastException: org.apache.activemq.command.BrokerId
at
org.apache.activemq.openwire.v2.MessageMarshaller.looseUnmarshal(MessageMarshaller.java:193)
at
org.apache.activemq.openwire.v2.ActiveMQMessageMarshaller.looseUnmarshal(ActiveMQMessageMarshaller.java:101)
at
org.apache.activemq.openwire.v2.ActiveMQStreamMessageMarshaller.looseUnmarshal(ActiveMQStreamMessageMarshaller.java:101)
at
org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.java:349)
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:273)
at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:156)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:136)
at java.lang.Thread.run(Thread.java:595)
I think this problem is caused by using backport-util-concurrent 3.0 on the
client side.
That's mentioned here:
https://issues.apache.org/jira/browse/GERONIMO-2995
Could AMQ client be made backport-util-concurrent 3.0 compatible?
I'm using ActiveMQ 4.1.1 . On the client side there's backport-util-concurrent
3.0 (server has backport-util-concurrent 2.1).
was (Author: lhotari):
I'm experiencing the same problem on the client side.
Exception in thread "ActiveMQ Transport: tcp://localhost/127.0.0.1:61616"
java.lang.ClassCastException: org.apache.activemq.command.BrokerId
at
org.apache.activemq.openwire.v2.MessageMarshaller.looseUnmarshal(MessageMarshaller.java:193)
at
org.apache.activemq.openwire.v2.ActiveMQMessageMarshaller.looseUnmarshal(ActiveMQMessageMarshaller.java:101)
at
org.apache.activemq.openwire.v2.ActiveMQStreamMessageMarshaller.looseUnmarshal(ActiveMQStreamMessageMarshaller.java:101)
at
org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.java:349)
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:273)
at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:156)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:136)
at java.lang.Thread.run(Thread.java:595)
I think this problem is caused by using backport-util-concurrent 3.0 on the
client side.
That's mentioned here:
https://issues.apache.org/jira/browse/GERONIMO-2995
Could AMQ client be made backport-util-concurrent 3.0 compatible?
I'm using ActiveMQ 4.1.1 which contains backport-util-concurrent 2.1.
> java.lang.ClassCastException: org.apache.activemq.command.BrokerId
> -------------------------------------------------------------------
>
> Key: AMQ-1169
> URL: https://issues.apache.org/activemq/browse/AMQ-1169
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.1.0
> Environment: winxp
> Reporter: Vadim Pesochinskiy
> Fix For: 4.1.1
>
>
> There were a lot of ": Channel was inactive for too long" messages before and
> after the ClassCastException. I do not know if the system would recover from
> this by itself.
> java.lang.ClassCastException: org.apache.activemq.command.BrokerId
> at
> org.apache.activemq.openwire.v2.MessageDispatchMarshaller.tightUnmarshal(MessageDispatchMarshaller.java:70)
> at
> org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.java:347)
> at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:273)
> at
> org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:156)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:136)
> at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
