[jboss-remoting-issues] [JBoss JIRA] Created: (JBREM-1129) Eliminate nondeterminism in Lease updates
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Thu May 7 03:43:46 EDT 2009
Eliminate nondeterminism in Lease updates
-----------------------------------------
Key: JBREM-1129
URL: https://jira.jboss.org/jira/browse/JBREM-1129
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.2.2.SP11, 2.5.0.SP2 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.2.SP12, 2.5.2 (Flounder)
Each time an org.jboss.remoting.LeasePinger sends a ping to a server side org.jboss.remoting.Lease, the ping message includes a sessionId for each org.jboss.remoting.Client connected to the server that holds the Lease. The lease updates its list of connected Clients each time it gets a ping, and it notifies all registered org.jboss.remoting.ConnectionListener's when a Client is removed from the list.
Since the default behavior of the socket (and bisocket) transports is to use a pool of connections, it is possible for ping messages to arrive out of order. There should be a timestamp on each ping message so that out of order messages can be discarded.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-remoting-issues
mailing list