TCP transport silently ignores java.net.SocketTimeoutException exceptions
-------------------------------------------------------------------------
Key: AMQ-2450
URL: https://issues.apache.org/activemq/browse/AMQ-2450
Project: ActiveMQ
Issue Type: Bug
Components: Transport
Affects Versions: 5.3.0, 4.1.2
Reporter: Trevor Pounds
Fix For: 4.1.3, 5.4.0
When a client is configured with a soTimeout query on a connection URI, the
exception gets caught and ignored inside the main TcpTransport class. From what
I can tell this has existed since 4.x. I'm not 100% sure if this is the
intended behavior but in our particular use case we are expecting the socket to
be closed after a period of no socket activity and reconnect again using the
failover transport logic. In my opinion it makes sense to throw this exception
out of the transport in the case where a slow broker may be taking too long to
service a request. I've narrowed down the offending code to the source file
[org.apache.activemq.transport.tcp.tcptransp...@204|http://fisheye6.atlassian.com/browse/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/transport/tcp/TcpTransport.java?r=HEAD#l204].
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
