[
https://issues.apache.org/jira/browse/AMQ-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-2605.
-----------------------------
Resolution: Cannot Reproduce
>From the log snippets given it appears as though there inactivity monitor
>detected a connection problem and closed the connection. The error in the
>TcpTransport can result from this due to a connection drop as it attempts to
>read a new message from the wire. Using failover to reconnect in this case
>would be a good start to improving stability.
> Unexpected error occured on TcpTransport caused by ClassCastException
> ---------------------------------------------------------------------
>
> Key: AMQ-2605
> URL: https://issues.apache.org/jira/browse/AMQ-2605
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.0
> Reporter: Mario Lukica
> Fix For: 5.x
>
>
> In setup with 2 brokers connected with ConduitBridge, we have a problem with
> network connector which is every couple of days disconnected because of
> ClassCastException on TcpTransport on other node.
> Network connector reconnects after some time (cca 1 min), but we have some
> minor message loss since we use syncSend=false on queues.
> - node1:
> {code}
> 15:07:59,160 DEBUG [Transport ] Transport failed:
> java.io.IOException: Unexpected error occured
> java.io.IOException: Unexpected error occured
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:192)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.ClassCastException
> 15:07:59,219 DEBUG [TransportConnection ] Stopping connection:
> /192.168.0.2:34586
> 15:07:59,220 DEBUG [TransportConnection ] Stopped transport:
> /192.168.0.2:34586
> {code}
> - node2:
> {code}
> 15:08:48,564 WARN [DemandForwardingBridge] Network connection between
> vm://broker02#1569160 and tcp://node1/192.168.0.1:62616 shutdown due to a
> remote error: org.apache.activemq.transport.InactivityIOException: Channel
> was inactive for too long: node1/192.168.0.1:62616
> 15:08:48,565 DEBUG [DemandForwardingBridge] The remote Exception was:
> org.apache.activemq.transport.InactivityIOException: Channel was inactive for
> too long: node1/192.168.0.1:62616
> org.apache.activemq.transport.InactivityIOException: Channel was inactive for
> too long: node1/192.168.0.1:62616
> at
> org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:168)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> 15:08:48,566 DEBUG [DemandForwardingBridge] stopping broker02 bridge to
> broker01
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
