socket client invoker connection pooling not bounded ---------------------------------------------------- Key: JBREM-586 URL: http://jira.jboss.com/jira/browse/JBREM-586 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.GA (Boon) Due to code change for JBREM-576, the socket client invoker's bounded connection pooling was broken and the pool became unbounded (due to reducing the scope of the pool being sychronized within MicroSocketClientInvoker.getConnection(). The fix for JBREM-576 needs to remain (so do not get dealock on disconnect of one client invoker while another is still in use). However, will also need to synchronize the increase/decrease of number of pooled connections in use. -- 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