Uploaded image for project: 'JBoss Remoting'
  1. JBoss Remoting
  2. JBREM-892

CLONE -Client side connection exception is not thrown on the client side when the lease times out [JBREM-888]

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.2.2.SP4
    • Fix Version/s: 2.2.2.SP7
    • Component/s: None
    • Labels:
      None
    • Workaround Description:
      Hide

      Increase the lease timeout, so that the lease does not time out on the client.
      This will not fix the problem, but it will stop the lease from timing out, by giving the client more time to establish the ping. This will effectively alleviate the problem.

      Show
      Increase the lease timeout, so that the lease does not time out on the client. This will not fix the problem, but it will stop the lease from timing out, by giving the client more time to establish the ping. This will effectively alleviate the problem.

      Description

      Clients that are connected that experience a lease timeout are not notified that they no longer have a connection on the server. The behavior is that clients think that they are alive, while they will no longer get any messages. Also something of note, the Server side pinger has been disabled for JBM.

      Note: this is an issue that can either be fixed on the remoting side or the JBM side. Discussing this with Clebert, it may be prudent to fix it on both sides. I've opened this jira to facilitate the communication about where the logic should go. Please refer to the linked jira for the JBM ticket that was opened for this same topic.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ron_sigal Ronald Sigal
                  Reporter:
                  jay.howell Jay Howell
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: