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:
      12

      Description

      Noticed the following when running jxtamgmt module test using run_client.
      C:\shoaln\shoal\gms>run_client.bat s1

      [#|2006-12-27T10:00:42
      .640-0800|FINER|JxtaMgmt|JxtaMgmt|_ThreadID=10;_ThreadName
      =main;ClassName=com.sun.enterprise.jxtamgmt.ClusterManager;MethodName=main;Recor
      dNumber=0;|Instance Name :clients1|#]

      [#|2006-12-27T10:00:53
      .375-0800|FINER|JxtaMgmt|JxtaMgmt|_ThreadID=10;_ThreadName
      =main;ClassName=com.sun.enterprise.jxtamgmt.ClusterManager;MethodName=<init>;Rec
      ordNumber=1;|Instance ID :urn:jxta:uuid-8C677192023A48AE9201BE8E2B2A84E44F1E44C3
      D2B94DCC91BDE9E6EE77374903|#]

      The time taken from the first log entry to the second is about 11 seconds
      (initial entry at 10:00:42 and second entry at 10:00:53).

      instance name s1 is used for the first time so I thought may be there is some
      jxta platform initialization cost. But the second run has the same startup time
      issue. It might be worth profiling this to find out where most time is being
      spent and if some optimizations are possible.

      Second Run (10 sec:
      C:\shoaln\shoal\gms>run_client.bat s1
      [#|2006-12-27T10:54:38
      .015-0800|FINER|JxtaMgmt|JxtaMgmt|_ThreadID=10;_ThreadName
      =main;ClassName=com.sun.enterprise.jxtamgmt.ClusterManager;MethodName=main;Recor
      dNumber=0;|Instance Name :clients1|#]

      [#|2006-12-27T10:54:48
      .781-0800|FINER|JxtaMgmt|JxtaMgmt|_ThreadID=10;_ThreadName
      =main;ClassName=com.sun.enterprise.jxtamgmt.ClusterManager;MethodName=<init>;Rec
      ordNumber=1;|Instance ID :urn:jxta:uuid-8C677192023A48AE9201BE8E2B2A84E44F1E44C3
      D2B94DCC91BDE9E6EE77374903|#]

        Activity

        Hide
        shreedhar_ganapathy added a comment -

        Latest checkin of jxta.jar from hamada addressed this issue. Brought down
        startup time from 10 secs on my machine to 1 sec.

        Show
        shreedhar_ganapathy added a comment - Latest checkin of jxta.jar from hamada addressed this issue. Brought down startup time from 10 secs on my machine to 1 sec.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: