[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1132) CLONE [JBREM-1128] - Introduce connection identity concept

CLONE [JBREM-1128] - Introduce connection identity concept ---------------------------------------------------------- Key: JBREM-1132 URL: https://jira.jboss.org/jira/browse/JBREM-1132 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public(Everyone can see) Affects Versions: 2.5.1 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Priority: Critical Fix For: 2.5.2 (Flounder) Currently, a Remoting server can monitor the continued connection to a Remoting client through the use of an org.jboss.remoting.LeasePinger / org.jboss.remoting.Lease pair. The client side LeasePinger sends out pings to the server side Lease, and, as long as the Lease receives timely pings, the connection is considered to be healthy. If a ping fails to arrive, then the Lease informs any registered org.jboss.remoting.ConnectionListener's about the connection failure. Consider the case in which an org.jboss.remoting.Client crashes, restarts, and recreates a LeasePinger in time for the new LeasePinger to satisfy its corresponding Lease. Then the Lease considers the connection to be intact. Some applications, however, with JBossMessaging being the prime example, might interpret this scenario as the failure and replacement of a connection. Remoting has no way of reporting a failure in this case. Remoting needs an optional behavior in which a connection is identified with a particular LeasePinger / Lease pair. When a LeasePinger is replaced, then a new connection begins. On the client side, the health of a connection can be reported by an org.jboss.remoting.ConnectionValidator, which periodically sends a ping to the server and reports a broken connection if it doesn't receive an answer within a configured window. The ConnectionValidator needs to be able to recognize and report on connections identifed by LeasePinger / Lease pairs.