"timfox" wrote : 2) and 3) should be handled the same on the server.
|
| In other words, the only case where we immediately remove the ServerSession is when we
get an explicit SESSION_CLOSE message.
|
This is not the case today: #2 results in a connectionDestroyed (with no clean-up) and #3
results in a connectionException(with immediate clean-up)
#3 needs to be fixed so that the server session is removed only when the connection TTL is
hit.
"timfox" wrote :
| Regarding the LAST request: we already have such a request; it's the SESSION_CLOSE
request.
When I receive the SESSION_CLOSE on the server, I flag the remoting connection as
"ready to be closed" once the server session has handled the packet.
In the remoting service, when I received a connectionDestroyed event, I check if the
remoting connection is ready to be closed.
If true (normal case), I remove the connection from the remoting service and destroy it.
else, I do nothing, the connection and the resources will be cleaned up when the
connection TTL is hit.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212973#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...