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

[Ron Sigal (JIRA)]

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

Unit tests:

  org.jboss.test.remoting.transport.bisocket.Bisocket.ConnectionPoolSizeTestCase
  org.jboss.test.remoting.transport.socket.ConnectionPoolSizeTestCase

> CLONE -MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools [JBREM-858]
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JBREM-870
>                 URL: http://jira.jboss.com/jira/browse/JBREM-870
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> 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