[jboss-jira] [JBoss JIRA] Commented: (JBREM-890) Fix thread pool eviction in socket transport

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-890?page=comments#action_12393537 ] 
            
Ron Sigal commented on JBREM-890:
---------------------------------

Two new variables in ServerThread determine if it is evictable.

1) invocationCount counts the number of invocations performed by the ServerThread with its current socket

A ServerThread which has performed zero invocations will not - at first - be evictable.  Otherwise, they could be evicted and reused while doing no useful work.

2) evictabilityTimeout determines how long to wait for an otherwise evictable ServerThread which has performed zero invocations.

evictabilityTimeout may be set with the configuration parameter ServerThread.EVICTABILITY_TIMEOUT (actual value "evictabilityTimeout"). The default is 10000 ms.  

> Fix thread pool eviction in socket transport
> --------------------------------------------
>
>                 Key: JBREM-890
>                 URL: http://jira.jboss.com/jira/browse/JBREM-890
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP4, 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> Currently org.jboss.rermoting.transport.socket.ServerThread.evict() attempts to interrupt a thread blocked on i/o in acknowledge() or readVersion() and return it to SocketServerInvoker.threadpool where it can be reused.  However, interrupt() will not normally unblock a thread in an i/o call.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira