[
https://jira.jboss.org/jira/browse/JBREM-1107?page=com.atlassian.jira.plu...
]
Ron Sigal updated JBREM-1107:
-----------------------------
Fix Version/s: (was: 2.5.0.SP3 (Flounder))
Affects Version/s: (was: 2.5.0.SP2 (Flounder) )
I'm removing 2.5.0.SP3 from the fix version list because the additional
synchronization introduced in version 2.4.0 should prevent this problem. In particular,
SocketServerInvoker$IdleTimeoutTask.run() calls the synchronized method
ServerThread.shutdown(), which can't be entered as long as the ServerThread is in the
synchronized method ServerThread.completeInvocation(), which is the case once ServerThread
reads an invocation and begins to process it.
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.2.SP12
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