sailfin
  1. sailfin
  2. SAILFIN-1732

JXTA connection to failed instance seemed to be tried 1 hr after failure detection

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: milestone 1
    • Component/s: session_replication
    • Labels:
      None
    • Environment:

      Operating System: Linux
      Platform: Other

      Description

      Parent Issue 1727.
      See parent issue for basic scenario steps.

      Time Line:
      2009-04-22T17:06:02 - Traffic started
      2009-04-22T21:06:56 - FAILURE_EVENT detected (failure inject a few seconds
      before that on instance110)

      • Test was allowed to run for 24x1
      • The failed instance was NOT restarted.
      • Steady Memory growth was observed on all other instances after failure.

      Logs Location:
      /net/asqe-logs.sfbay.sun.com//export1/SailFin/Results/ST/2.0/subscribe-refresh-failure/fail/b10-1failures-mem-growth/

      The following messages appear in the log indicating some jxta activity to the
      failed instance ~1 1/2 hour after failure was detected. This message continues
      to appear periodically for about an hour after it starts and then stops. This
      happens on all the instances.

      [#|2009-04-22T22:58:36.619+0530|WARNING|sun-glassfish-comms-server1.5|com.sun.enterprise.ee.web.sessmgmt|_ThreadID=54;_ThreadName=ReplicationUnicastSenderExecutor

      • 14;_RequestID=1d310ce5-fd9b-4fc5-a30c-4874ffc312ec;|Waited 5 seconds for free
        JXTA unicast pipe to instance110|#]

        Issue Links

          Activity

          Hide
          varunrupela added a comment -

          Added keyword and dependency

          Show
          varunrupela added a comment - Added keyword and dependency
          Hide
          Scott Oaks added a comment -

          There are two parts to this fix. First, we need to keep track of the cluster
          state for the JxtaUnicastPipes (like we do for the JxtaUnicastSenders map)
          because it can take too long for the socket to timeout otherwise. That will
          prevent the Waited 5 seconds for free socket messages and any spurious attempts
          to send data after the instance is down.

          The bug also mentions memory growth; is that at all different from the memory
          growth reported in 1724 and or 1731? I'm suspecting it is the same, so that's
          not being addressed here.

          Checking in JoinNotificationEventHandler.java;
          /cvs/glassfish/appserv-core-ee/http-session-persistence/src/java/com/sun/enterprise/ee/web/sessmgmt/JoinNotificationEventHandler.java,v
          <-- JoinNotificationEventHandler.java
          new revision: 1.11.2.16; previous revision: 1.11.2.15
          done
          Checking in JxtaReplicationSender.java;
          /cvs/glassfish/appserv-core-ee/http-session-persistence/src/java/com/sun/enterprise/ee/web/sessmgmt/JxtaReplicationSender.java,v
          <-- JxtaReplicationSender.java
          new revision: 1.18.2.44; previous revision: 1.18.2.43
          done
          Checking in JxtaUnicastPipeUtil.java;
          /cvs/glassfish/appserv-core-ee/http-session-persistence/src/java/com/sun/enterprise/ee/web/sessmgmt/Attic/JxtaUnicastPipeUtil.java,v
          <-- JxtaUnicastPipeUtil.java
          new revision: 1.1.2.2; previous revision: 1.1.2.1
          done

          Show
          Scott Oaks added a comment - There are two parts to this fix. First, we need to keep track of the cluster state for the JxtaUnicastPipes (like we do for the JxtaUnicastSenders map) because it can take too long for the socket to timeout otherwise. That will prevent the Waited 5 seconds for free socket messages and any spurious attempts to send data after the instance is down. The bug also mentions memory growth; is that at all different from the memory growth reported in 1724 and or 1731? I'm suspecting it is the same, so that's not being addressed here. Checking in JoinNotificationEventHandler.java; /cvs/glassfish/appserv-core-ee/http-session-persistence/src/java/com/sun/enterprise/ee/web/sessmgmt/JoinNotificationEventHandler.java,v <-- JoinNotificationEventHandler.java new revision: 1.11.2.16; previous revision: 1.11.2.15 done Checking in JxtaReplicationSender.java; /cvs/glassfish/appserv-core-ee/http-session-persistence/src/java/com/sun/enterprise/ee/web/sessmgmt/JxtaReplicationSender.java,v <-- JxtaReplicationSender.java new revision: 1.18.2.44; previous revision: 1.18.2.43 done Checking in JxtaUnicastPipeUtil.java; /cvs/glassfish/appserv-core-ee/http-session-persistence/src/java/com/sun/enterprise/ee/web/sessmgmt/Attic/JxtaUnicastPipeUtil.java,v <-- JxtaUnicastPipeUtil.java new revision: 1.1.2.2; previous revision: 1.1.2.1 done
          Hide
          Scott Oaks added a comment -

          Fixed with previous checkin.

          Show
          Scott Oaks added a comment - Fixed with previous checkin.

            People

            • Assignee:
              Scott Oaks
              Reporter:
              varunrupela
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: