[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1107) SocketServerInvoker.IdleTimeoutTask interrupts ServerThreads during long invocation
[
https://jira.jboss.org/jira/browse/JBREM-1107?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1107:
----------------------------------
Fixed org.jboss.remoting.transport.socket.SocketServerInvoker$IdleTimeoutTask so that it
will not kill an org.jboss.remoting.transport.socket.ServerThread that's in the middle
of an invocation.
Unit test:
org.jboss.test.remoting.transport.socket.timeout.idle.SafeIdleTimeoutTestCase.
Also, committed the same unit test on the 2.x branch, just to verify that the 2.x version
of SocketServerInvoker can pass the test with no changes.
Waiting for results in hudson.
Note: It might be worth updating the Remoting Guide to point out that a ServerThread in
the middle of a long running invocation will still be harvested by IdleTimeoutTask if the
idle timeout has expired.
SocketServerInvoker.IdleTimeoutTask interrupts ServerThreads during
long invocation
-----------------------------------------------------------------------------------
Key: JBREM-1107
URL: https://jira.jboss.org/jira/browse/JBREM-1107
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.2.SP11
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.3.SP1
org.jboss.remoting.transport.socket.SocketServerInvoker.IdleTimerTask is intended to shut
down org.jboss.remoting.transport.socket.ServerThreads that haven't been in use for
some configured amount of time. For each ServerThread, it compares the value of
System.currentTimeMillis() to the time at which the ServerThread last started or finished
processing an invocation, and, if the difference exceeds the value of the
"idleTimeout" parameter, it shuts down the ServerThread.
The problem is that if processing an invocation takes longer than the value of
"idleTimeout", a ServerThread could be shut down DURING the processing of an
invocation.
--
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