]
Ron Sigal updated JBREM-858:
----------------------------
Fix Version/s: (was: 2.4.0.Beta1 (Pinto))
Removed fix version 2.4.0.Beta1 - it's cloned by JBREM-870.
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.SP4
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: