[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1120) Add a socket write timeout facility

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBREM-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12481484#action_12481484 ] 

Ron Sigal commented on JBREM-1120:
----------------------------------

In the presence of the configuration parameter org.jboss.remoting.transport.socket.SocketWrapper.WRITE_TIMEOUT (actual value "writeTimeout"), the socket and bisocket transports will impose a timeout on write() operations.  The parameter value is given in milliseconds, and it can be configured by way of the InvokerLocator, configuration maps, MBean XML files, or a ServerConfiguration object (in Remoting 2.4/2.5).  The facility works on both the client and server sides, and it applies to both ordinary invocations and callbacks.

Unit tests:

  * org.jboss.remoting.transport.bisocket.ssl.SSLBisocketWriteTimeoutTestCase
  * org.jboss.remoting.transport.bisocket.BisocketWriteTimeoutTestCase
  * org.jboss.remoting.transport.socket.ssl.SSLSocketWriteTimeoutTestCase
  * org.jboss.remoting.transport.socket.SocketWriteTimeoutTestCase

Tests are passing in hudson.

The facility has been implemented on the 2.x branch.

Still need to:

1. port the facility to the 2.2 branch, and
2. update the Remoting Guides. 

> Add a socket write timeout facility
> -----------------------------------
>
>                 Key: JBREM-1120
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1120
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP11, 2.5.1 (Flounder)
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.5.2 (Flounder), 2.2.3.SP1
>
>
> The timeout parameter of Java sockets applies only to reading.  But a write to a bad connection will hang until the underlying TCP implementation detects the problem.  
> A timer that monitors blocked write operations would be useful.

-- 
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