ort.InactivityMonitor.onCommand(InactivityMonitor.java:206)
>>>>at
>>>> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
>>>>at
>>>> org.apache.activemq.transport.tcp.TcpTransport.doRun
rt.tcp.TcpTransport.run(TcpTransport.java:183)
>>> at java.lang.Thread.run(Thread.java:619)
>>>
>>> This seems to be already captured as an issue:
>>> https://issues.apache.org/activemq/browse/AMQ-1687
>>>
>>> Any idea when there will be a patch
run(Thread.java:619)
>>
>> This seems to be already captured as an issue:
>> https://issues.apache.org/activemq/browse/AMQ-1687
>>
>> Any idea when there will be a patch for this? Is there a work around?
>>
>> It seems like the messages are getting to the
mq/browse/AMQ-1687
>
> Any idea when there will be a patch for this? Is there a work around?
>
> It seems like the messages are getting to the listeners ok even though
> broker is spitting out the errors above. But I want to make sure that there
> would be no we
listeners ok even though
broker is spitting out the errors above. But I want to make sure that there
would be no weird side-effects due to the error.
Thanks you in advance
jydev
--
View this message in context:
http://www.nabble.com/ClassCastException-with-VirtualTopic-on-5.1
