dev@shoal.java.net

Re: JoinedAndReady Notification

From: Kazem Ardekanian <Kazem.Ardekanian_at_Sun.COM>
Date: Tue, 19 Feb 2008 13:21:52 -0800

Hello Sheetal,

The log lines containing JoinedAndReadyNotification do not convey any
information about 'who' has joined and ready.

As an example, the JoinedAndReady log lines below belong to an instance
of a 8-node cluster (using the latest build).

Please let me know how to find out about the name of the joinedAndReady
cluster member.

Thanks,
Kazem

[#|2008-02-19T12:13:48.299-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
join and ready signal|#]

[#|2008-02-19T12:13:48.309-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
: processing a received signal
com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]

[#|2008-02-19T12:13:48.720-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
join and ready signal|#]

[#|2008-02-19T12:13:48.721-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
: processing a received signal
com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]

[#|2008-02-19T12:13:51.113-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
join and ready signal|#]

[#|2008-02-19T12:13:51.114-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
: processing a received signal
com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]

[#|2008-02-19T12:13:51.446-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=10;_ThreadName=main;ClassName=com.sun.enterprise.ee.cms.impl.common.GroupManagementServiceImpl;MethodName=reportJoinedAndReadyState;_RequestID=7810caa6-2eac-4f33-a5de-e0685f60417b;|GMS:Reporting
Joined and Ready state to group clusterz1|#]

[#|2008-02-19T12:13:51.450-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=10;_ThreadName=main;ClassName=com.sun.enterprise.jxtamgmt.HealthMonitor;MethodName=reportJoinedAndReadyState;_RequestID=7810caa6-2eac-4f33-a5de-e0685f60417b;|Calling
reportMyState() with READY...|#]

[#|2008-02-19T12:13:51.615-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
join and ready signal|#]

[#|2008-02-19T12:13:51.616-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
: processing a received signal
com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]

[#|2008-02-19T12:13:56.678-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
join and ready signal|#]

[#|2008-02-19T12:13:56.680-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
: processing a received signal
com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]

[#|2008-02-19T12:13:56.892-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
join and ready signal|#]

[#|2008-02-19T12:13:56.894-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
: processing a received signal
com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]


Sheetal Vartak wrote, On 02/11/08 14:44:
> Hi Kazem,
> Just wanted to let you know that a new feature was added around November
> of last year. The feature was about adding a new notification for
> instances which have joined the group and are ready for processing
> client requests. This notification is different from the Join
> notification. The Join notification only tells the other instances that
> a particular instance has joined the group. It does not mean that the
> instance is completely up and ready to serve.
> You can read more about this on Shreedhar's blog :
> http://blogs.sun.com/shreedhar/date/20080117
>
> This new feature needs to be tested. Testing will be very simple and all
> we need to know is if each of the instances in a group send out the
> JoinedAndReadyEvent. Since instances start at different times, its
> possible that an instance A will not see this event from instance B.
> This is perfectly acceptable. All we need to know is that instances A
> and B have sent out this event.
>
> Please let me know if you have any other questions.
>
> Thanks
> Sheetal
>