[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1189) Graceful connection close

[David Lloyd (JIRA)]

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

David Lloyd commented on JBREM-1189:
------------------------------------

Immediate shutdown would be for doing a hard shutdown of the container or system for example, or when the wait time for close to finish is more expensive than the loss of connection, or when you've initiated a graceful close and some time has elapsed and you just want the connection to go away.

IoFuture is a possibility.  Cancel wouldn't work (obviously).  It's not clear though how results would be handled if two threads called closeAsync().  With close() only one thread would get a result; but if the expected semantics of closeAsync() were to be to await the close finish, that rule would be broken, and close exceptions might be delivered to multiple threads.  I guess overall I don't like it - it would be the only case anywhere that more than one IoFuture can exist for the same event that I can think of.  The correct semantics would be very hard to figure out.

awaitClose() has no side effects other than simply waiting for the resource to be closed.

> Graceful connection close
> -------------------------
>
>                 Key: JBREM-1189
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1189
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: r3 core: api, r3 core: remote
>            Reporter: David Lloyd
>             Fix For: 3.1.0.Beta2
>
>
> Design a mechanism for graceful connection shutdown.  This could work in one of a few ways:
> 1. Refuse new clients, immediately close all clients, allow outstanding requests to finish
> 2. Refuse new clients, keep connection up until all clients are closed and all outstanding requests to finish
> #1 might be better - since requests have a finite lifespan but clients can hang around indifinitely.

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