[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1123) SocketServerInvoker needs an immediate shutdown option
[
https://jira.jboss.org/jira/browse/JBREM-1123?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1123:
----------------------------------
Added an "immediateShutdown" bean property to SocketServerInvoker and a new
unsynchronized method, shutdownImmediately() to ServerThread. If immediateShutdown is
true, then SocketServerInvoker.cleanup(), called by SocketServerInvoker.stop(), will call
ServerThread.shutdownImmediately() instead of the synchronized method
ServerThread.shutdown().
Unit tests:
* org.jboss.test.remoting.transport.socket.shutdown.BisocketImmediateShutdownTestCase
* org.jboss.test.remoting.transport.socket.shutdown.SocketImmediateShutdownTestCase
Waiting for results in hudson.
SocketServerInvoker needs an immediate shutdown option
------------------------------------------------------
Key: JBREM-1123
URL: https://jira.jboss.org/jira/browse/JBREM-1123
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.1 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.2 (Flounder)
org.jboss.remoting.transport.socket.SocketServerInvoker won't shut down while any
ServerThreads are in the middle of an invocation. It might be useful to have an option to
shut down immediately to prevent rogue ServerInvocationHandlers from preventing the server
from shutting down.
--
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