Hi Christian
Christian Brennsteiner wrote:
> i have somehow managed to srew up my shoal test case. when i try to
> run it on my mashien it gives the following output and then consumes
> 100% CPU
>
> run-single:
> 28.06.2008 16:45:45 spar.eai.test.SimpleGMSSample runSimpleSample
> INFO: Starting SimpleGMSSample....
> 28.06.2008 16:45:45 spar.eai.test.SimpleGMSSample initializeGMS
> INFO: Initializing Shoal for member: server1214664345142 group:Group1
> 28.06.2008 16:45:45 spar.eai.test.SimpleGMSSample registerForGroupEvents
> INFO: Registering for group event notifications
> 28.06.2008 16:45:45 spar.eai.test.SimpleGMSSample joinGMSGroup
> INFO: Joining Group Group1
Is the test hanging at this point? Do you see any stack trace here ?
Can you try a jstack <pid> or kill -3 <pid> here?
> it is running within netbeans.
> i have seen that shoal creates some folders on the disk. (.shoal) when
> i remove them it works fine again.
Sounds very familiar. We had this problem back in August 07 when GF v2
was about to ship and I remember the Jxta jar contained a fix for this.
When you see this cpu spike up again, can you do a ls -lrt a few times
with a gap of say 2 minutes on the .shoal directory and post it here?
> so now my question is is this a bug?
This was a bug. And it was fixed and since then two update releases of
GlassFish have shipped without this problem. (GF has extensive QE
testing including tests like longevity, stress, load based functional
testing, etc for each release to ensure there are no regressions). It
would be helpful to know what platform you are running on.
> i am planning to use shoal within GFv2.2 if something like this would
> occur in my production systems i would not be that happy about it. i
> am using "shoal-1.0ur_11142007"
That is a stable version with fixes for this 100% CPU issue and a memory
leak in the Jxta jar. It would help to have a Jstack/kill -3 output and
the listing sizes of files in the .shoal directory to see if a problem
still exists. Could you tell us which OS platform are you running on?
And what is your expected going live date on production?
>
> any ideas?
>
> regards chris