shoal
  1. shoal
  2. SHOAL-11

GMS doesn't see nodes via GroupHandle that have been started later

    Details

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

      Operating System: All
      Platform: All

    • Issuezilla Id:
      11

      Description

      slightly modify ApplicationServer.java:

      ===

      public void run() {
      startGMS();
      addMemberDetails();
      startClientServices();
      long till = System.currentTimeMillis()
      + Integer.parseInt(System.getProperty("LIFEINMILLIS", "15000"));
      try {
      do {
      for (String details : gms.getGroupHandle()
      .getAllCurrentMembersWithStartTimes())

      { logger.log(Level.INFO, details); }

      Thread.sleep(3000);
      } while (System.currentTimeMillis() < till);
      } catch (InterruptedException e)

      { logger.log(Level.SEVERE, e.getLocalizedMessage()); }

      stopClientServices();
      stopGMS();
      System.exit(0);
      }

      ===

      try this in separate consoles

      ./rungmsdemo.sh inst1 grp0 CORE 60000 INFO
      ./rungmsdemo.sh inst2 grp0 CORE 60000 INFO

      My output is (only relevant snippets here):

      #1:

      [#|2006-12-26T21:10:35.840+0300|INFO|JxtaMgmt|javax.ee.enterprise.system.gms|_ThreadID=11;
      _ThreadName=ApplicationServer;ClassName=com.sun.enterprise.ee.cms.tests.ApplicationServer;
      MethodName=run;RecordNumber=90;

      inst1::1167156573930 #]

      [#|2006-12-26T21:10:35.937+0300|FINER|JxtaMgmt|javax.ee.enterprise.system.gms|_ThreadID=18;
      _ThreadName=HealthMonitor Thread interval : 3000;
      ClassName=com.sun.enterprise.jxtamgmt.MasterNode;MethodName=isMaster;RecordNumber=91;

      isMaster :true MasterAssigned :true View Size :2 #]

      #2:

      [#|2006-12-26T21:10:36.529+0300|FINER|JxtaMgmt|javax.ee.enterprise.system.gms|_ThreadID=22;
      _ThreadName=HealthMonitor Thread interval : 3000;
      ClassName=com.sun.enterprise.jxtamgmt.MasterNode;MethodName=isMaster;RecordNumber=113;

      isMaster :false MasterAssigned :true View Size :2 #]

      [#|2006-12-26T21:10:36.540+0300|INFO|JxtaMgmt|javax.ee.enterprise.system.gms|_ThreadID=11;
      _ThreadName=ApplicationServer;ClassName=com.sun.enterprise.ee.cms.tests.ApplicationServer;
      MethodName=run;RecordNumber=114;

      inst2::1167156586641 #]

      [#|2006-12-26T21:10:36.540+0300|INFO|JxtaMgmt|javax.ee.enterprise.system.gms|_ThreadID=11;
      _ThreadName=ApplicationServer;ClassName=com.sun.enterprise.ee.cms.tests.ApplicationServer;
      MethodName=run;RecordNumber=115;

      inst1::1167156573930 #]

      --------------------------

      Why #1 does only see itself, but both of them say that ViewSize is 2 ???

        Activity

        Hide
        xmart added a comment -

        Yes, I use a jar that I built max. 1 hour before the last post.

        There is a problem in log4j-commonslogging junction while commons-logging tries
        to work with both log4j1.2 and 1.3... and it doesn't work well without it))

        Show
        xmart added a comment - Yes, I use a jar that I built max. 1 hour before the last post. There is a problem in log4j-commonslogging junction while commons-logging tries to work with both log4j1.2 and 1.3... and it doesn't work well without it))
        Hide
        shreedharganapathy added a comment -

        One more question:
        Are you using the jxta jar that is supplied with the build (provided in lib dir)?

        Show
        shreedharganapathy added a comment - One more question: Are you using the jxta jar that is supplied with the build (provided in lib dir)?
        Hide
        xmart added a comment -

        Both the bundled jxta.jar and jxta-2.4.1b.jar work.
        However, jxta-2.4.1b.jar generates substantially more log output.

        May you describe the differences between these? Just different versions or the
        one bundled is patched?

        Show
        xmart added a comment - Both the bundled jxta.jar and jxta-2.4.1b.jar work. However, jxta-2.4.1b.jar generates substantially more log output. May you describe the differences between these? Just different versions or the one bundled is patched?
        Hide
        shreedharganapathy added a comment -

        I looked at the sources of jxta and needless to say IDFactory does use log4j
        classes. I suppose we may have a patched version of jxta to remove this
        dependency as with the version of jxta jar we have in Shoal I dont see this
        stack trace you reported.

        I will let hamada respond on that as he is also the Jxta architect.

        Show
        shreedharganapathy added a comment - I looked at the sources of jxta and needless to say IDFactory does use log4j classes. I suppose we may have a patched version of jxta to remove this dependency as with the version of jxta jar we have in Shoal I dont see this stack trace you reported. I will let hamada respond on that as he is also the Jxta architect.
        Hide
        hamada added a comment -

        The bundled jxta.jar is based on 2.4.1 with patch
        http://platform.jxta.org/issues/show_bug.cgi?id=1537, and some select fixes from
        the upcoming jxta release, as we try to limit the number of changes introduced.
        Once issue 1537 is applied you can expect alignment with the JXTA stable releases.

        Show
        hamada added a comment - The bundled jxta.jar is based on 2.4.1 with patch http://platform.jxta.org/issues/show_bug.cgi?id=1537 , and some select fixes from the upcoming jxta release, as we try to limit the number of changes introduced. Once issue 1537 is applied you can expect alignment with the JXTA stable releases.

          People

          • Assignee:
            shreedharganapathy
            Reporter:
            xmart
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: