[JBoss JIRA] Created: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
4:38 p.m.
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
5 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=comments#action_12390368 ]
Ron Sigal commented on JBREM-858:
---------------------------------
Fix applied to branch 2.2.2.GA_CP.
Unit tests:
org.jboss.test.remoting.transport.bisocket.Bisocket.ConnectionPoolSizeTestCase
org.jboss.test.remoting.transport.socket.ConnectionPoolSizeTestCase
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
10:26 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal updated JBREM-858:
----------------------------
Fix Version/s: 2.2.2.SP3
2.4.0.Beta1 (Pinto)
(was: 2.2.2.GA_CP03)
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.SP3, 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
7:36 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal updated JBREM-858:
----------------------------
Fix Version/s: (was: 2.2.2.SP3)
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.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
7:38 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal updated JBREM-858:
----------------------------
Fix Version/s: 2.2.2.SP3
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.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), 2.2.2.SP3
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
7:41 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal updated JBREM-858:
----------------------------
Fix Version/s: (was: 2.4.0.Beta1 (Pinto))
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.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.2.SP3
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
7:43 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal closed JBREM-858.
---------------------------
Resolution: Done
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.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.2.SP3
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
7:50 p.m.
New subject: [JBoss JIRA] Reopened: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal reopened JBREM-858:
-----------------------------
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.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.2.SP3
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
7:52 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal updated JBREM-858:
----------------------------
Fix Version/s: 2.2.2.SP4
(was: 2.2.2.SP3)
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.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:54 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal closed JBREM-858.
---------------------------
Resolution: Done
Moved to 2.2.2.SP4.
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.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:59 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal closed JBREM-858.
---------------------------
Resolution: Done
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.4.0.Beta1 (Pinto), 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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:59 p.m.
New subject: [JBoss JIRA] Reopened: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal reopened JBREM-858:
-----------------------------
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, 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
11:59 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal updated JBREM-858:
----------------------------
Fix Version/s: 2.4.0.Beta1 (Pinto)
Added fix version 2.4.0.Beta1 - see JBREM-975 "Make sure all fixes on 2.2 branch are
applied to 2.x branch".
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, 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
12:09 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:09 a.m.
New subject: [JBoss JIRA] Reopened: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal reopened JBREM-858:
-----------------------------
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:10 a.m.
New subject: [JBoss JIRA] Closed: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools
[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ]
Ron Sigal closed JBREM-858.
---------------------------
Resolution: Done
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6633
days inactive
6805
days old
15 comments
1 participants
participants (1)
-
Ron Sigal (JIRA)