[
https://jira.jboss.org/jira/browse/JBREM-1146?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1146:
----------------------------------
On branch 2.2, extended generalized SocketException facility with regular expression.
On branch 2.x, added generalized SocketException facility.
Unit tests:
org.jboss.test.remoting.transport.socket.socketexception.GeneralizeSocketExceptionTestCase
.
Waiting for results from hudson.
Need to update Remoting Guide.
Treat IOException("Connection reset by peer") as a
retriable exception
----------------------------------------------------------------------
Key: JBREM-1146
URL:
https://jira.jboss.org/jira/browse/JBREM-1146
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.1 (Flounder), 2.2.3
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.2 (Flounder), 2.2.3.SP1
org.jboss.remoting.transport.socket.MicroSocketClientInvoker uses the parameter
"numberOfCallRetries" to determine the number of invocation attempts to make
upon receiving java.net.SocketExceptions. For example, SocketException("Connection
reset") will cause MicroSocketClientInvoker to get another socket and try again.
However, if a connection is reset on the other side, then an IOException("Connection
reset by peer") is thrown, which doesn't lead to a retry. It should be possible
to configure the socket transport to treat an IOException("Connection reset by
peer") as retriable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira