activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-2606) Unexpected error occured on TcpTransport caused by ArrayIndexOutOfBoundsException
Date Fri, 30 Sep 2011 21:23:45 GMT

     [ https://issues.apache.org/jira/browse/AMQ-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQ-2606.
-----------------------------

    Resolution: Not A Problem

Working as designed, exceptions on loss of connection due to incomplete openwire commands
being read are acceptable.  The static connection will reconnect once the connection is dropped.
                
> Unexpected error occured on TcpTransport caused by ArrayIndexOutOfBoundsException
> ---------------------------------------------------------------------------------
>
>                 Key: AMQ-2606
>                 URL: https://issues.apache.org/jira/browse/AMQ-2606
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Mario Lukica
>             Fix For: 5.x
>
>
> Problem is basically a copy of AMQ-2605, but caused by different exception on TcpTransport.
> 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) by inactivity checker, but we
have some minor message loss since we use syncSend=false on queues.
> {code}
> 15:18:37,771 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.ArrayIndexOutOfBoundsException
> 15:18:37,772 DEBUG [TransportConnection ] Stopping connection: /192.168.0.2:36222
> 15:18:37,829 DEBUG [TransportConnection ] Stopped transport: /192.168.0.2:36222
> 15:18:37,829 DEBUG [TransportConnection ] Cleaning up connection resources: /192.168.0.2:36222
> {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

        

Mime
View raw message