Details

      Description

      When a rejoin event happens (an instance fails and restarts before GF knows it has failed), the status for it in 'asadmin get-health' shows started instead of rejoined. This is happening because the rejoin subevent is null in the JoinedAndReadyNotificationSignal. Am filing this for GF integration and will file a more technical one against Shoal to get the fix in.

      This is a minor issue now because instances probably won't restart this quickly. But it would be good to get the fix in. To cause this, here's a snippet of domain.xml that leads to an absurdly long time to kill/restart an instance:

      <group-management-service>
      <failure-detection
      heartbeat-frequency-in-millis="1800000"
      max-missed-heartbeats="30"></failure-detection>
      </group-management-service>

        Issue Links

          Activity

          Hide
          Bobby Bissett added a comment -

          Adding dependency.

          Show
          Bobby Bissett added a comment - Adding dependency.
          Hide
          Bobby Bissett added a comment -

          This has been fixed in the shoal workspace and will be in the next integration of shoal into glassfish.

          Show
          Bobby Bissett added a comment - This has been fixed in the shoal workspace and will be in the next integration of shoal into glassfish.
          Hide
          Bobby Bissett added a comment -

          Fixed in revision 45770.

          Show
          Bobby Bissett added a comment - Fixed in revision 45770.

            People

            • Assignee:
              Bobby Bissett
              Reporter:
              Bobby Bissett
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: