[JBoss JIRA] Created: (JBREM-612) Verify push callback connection with multiplex transport shares client to server connection.
1:43 a.m.
Verify push callback connection with multiplex transport shares client to server
connection.
--------------------------------------------------------------------------------------------
Key: JBREM-612
URL: http://jira.jboss.com/jira/browse/JBREM-612
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.2.0.Beta1 (Bluto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Priority: Minor
Fix For: 2.2.0.Beta1 (Bluto)
Want to add a unit test that shows that when one of the Client.addlistener() methods with
no InvokerLocator parameter creates an anonymous callback Connector, the callback
connection from the server to the client reuses the connection from the client to the
server.
--
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
1:51 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-612) Verify push callback connection with multiplex transport shares client to server connection.
[ http://jira.jboss.com/jira/browse/JBREM-612?page=comments#action_12345636 ]
Ron Sigal commented on JBREM-612:
---------------------------------
Found a loophole in MultiplexClientInvoker which would all the callback connection to
reuse an existing connection that was different from the client to server connection. In
particular, MultiplexClientInvoker.getCallbackLocator() should add MULTIPLEX_BIND_HOST and
MULTIPLEX_BIND_PORT so that when the server side MultiplexClientInvoker looks for a
MultiplexingManager, it will search on both endpoints. This must be the same connection
used by the client which initiated the callback connection.
Verify push callback connection with multiplex transport shares
client to server connection.
--------------------------------------------------------------------------------------------
Key: JBREM-612
URL: http://jira.jboss.com/jira/browse/JBREM-612
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.Beta1 (Bluto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Priority: Minor
Fix For: 2.2.0.Beta1 (Bluto)
Want to add a unit test that shows that when one of the Client.addlistener() methods with
no InvokerLocator parameter creates an anonymous callback Connector, the callback
connection from the server to the client reuses the connection from the client to the
server.
--
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
1:53 a.m.
New subject: [JBoss JIRA] Closed: (JBREM-612) Verify push callback connection with multiplex transport shares client to server connection.
[ http://jira.jboss.com/jira/browse/JBREM-612?page=all ]
Ron Sigal closed JBREM-612.
---------------------------
Resolution: Done
Changed MultiplexClientInvoker.getCallbackLocator() according to previous note.
Verify push callback connection with multiplex transport shares
client to server connection.
--------------------------------------------------------------------------------------------
Key: JBREM-612
URL: http://jira.jboss.com/jira/browse/JBREM-612
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.Beta1 (Bluto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Priority: Minor
Fix For: 2.2.0.Beta1 (Bluto)
Want to add a unit test that shows that when one of the Client.addlistener() methods with
no InvokerLocator parameter creates an anonymous callback Connector, the callback
connection from the server to the client reuses the connection from the client to the
server.
--
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
6573
days inactive
6573
days old
2 comments
1 participants
participants (1)
-
Ron Sigal (JIRA)