Sorry for the delay in responding.
Could you share your test program so we can reproduce this issue?
Also how are you starting the group members - simultaneously, one after
another, starting one first then rest of the members simultaneously ?
I have promoted the Shoal 1.0 FCS bits to Shoal website. These bits went
into GlassFish v2 FCS release that happened earlier this week.
https://shoal.dev.java.net/files/documents/5135/69556/shoal-1.0_08302007.zip
This contains a fix in Jxta for a high cpu utilization bug that was
reported in GF testing. Could you try with these bits and let us know?
We will try a modified test with your case of no JoinNotification
registration.
Thanks
Shreedhar
Markus.Hampel_at_tk-online.de wrote:
>
> Hello,
>
> I'm currently evaluating Shoal and observed the following strange
> behavior:
>
> - If there is NO JoinNotificationActionFactory registered, the second
> process in a group needs for about 10 - 20 sec. full CPU after
> starting the GMSModule.
>
> - After starting a process for a group, that already has some members,
> the process sometimes gets JoinNotifications from all members,
> sometimes only from one member (I couldn't recognize a pattern for the
> behavior).
>
> Thanks,
> Markus