[ http://jira.jboss.com/jira/browse/JBREM-890?page=comments#action_12393337 ] Ron Sigal commented on JBREM-890: --------------------------------- Various changes have been made to the server side of the socket transport in response to JBREM-821 "JBoss Remoting fails under load". In particular, 2) The connector close process is not clean. I would suggest the code should be changed so the server threads are shut down at the beginning of the connector close process. I.e. a) Wait for current invocations on that server invoker to complete - and don't allow any more. b) Once all are complete shut it down. Additional synchronization was added in response. However, one mistake was to synchronize ServerThread.evict(). The problem is that the SocketServerInvoker AcceptorThread could call ServerThread.evict() while the ServerThread was in the synchronized method completeInvocation(), which could leave the AcceptorThread blocked while a different ServerThread returned itself to the threadpool. ServerThread has been changed so that ServerThread.evict() is not synchronized, but a synchronized flag is added so that evict() will shut down the ServerThread's SocketWrapper only if the ServerThread is in Acknowledge() or readVersion(). ServerThread.evict() has also been changed to return a boolean value which indicates if the eviction attempt (i.e., closing the SocketWrapper) was attempted. org.jboss.remoting.transport.socket.LRUPool, which is the type of SocketServerInvoker.clientpool - which holds ServerThreads currently in use, has been changed to loop through the used threads until a call to ServerThread.evict() returns true. If no such ServerThread exists, LRUPool will set a flag which can be retrieved with the new method LRUPool.getEvictionNeeded(). At the top of each loop in doRun(), ServerThread will call LRUPool.getEvictionNeeded() and return itself to SocketServerInvoker.threadpool - which holds unused ServerThreads - if getEvictionNeeded() returns true. -- 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

[ 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. -- 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