[jboss-jira] [JBoss JIRA] Created: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools

[Ron Sigal (JIRA)]

MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
-----------------------------------------------------------------------------------

                 Key: JBREM-858
                 URL: http://jira.jboss.com/jira/browse/JBREM-858
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
             Fix For: 2.2.2.GA_CP03


If two instances of org.jboss.remoting.Client are created, one with clientMaxPoolSize=1 and one with clientMaxPoolSize=30, they will still share the same connection pool because the key to the connection pools, org.jboss.remoting.transport.socket.ServerAddress, does not include the value of clientMaxPoolSize.  ServerAddress.equals() and ServerAddress.hashCode() should be modified to include the value of clientMaxPoolSize.

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