Re: [stellation-res] Latest checkin *does* run the unit tests - with one

["Mark C. Chu-Carroll" <mcc@xxxxxxxxxxxxxx>]

On Wednesday 14 August 2002 04:38 pm, Florin Iucha wrote:
> On Wed, Aug 14, 2002 at 11:54:33AM +0000, Mark C. Chu-Carroll wrote:
> >                                                                      in
> > which case you'd see a communication core thread, plus the message queue
> > thread pool, for each of the invocations. The default message pool is 5
> > threads, producing, I think, 8 client-side threads per invocation. 
> > (Hmmm... I wonder if the message handler thread pool is terminating
> > threads correctly on engine shutdown... I'll check that.)
> >
> > This wouldn't explain 1000 threads,
>
> 5 tests * (15 checkins + 15 checkouts + 1 list version + 5 adds) * 8
> threads - we are pretty close

It appears that's it. The server wasn't properly collecting the message 
delivery thread pool, and running in the unit tests, those threads stayed 
live.

Testing somewhat informally, I find that between Eclipes, a Stellation server, 
and some other IBM Java software that I run, I've got 49 java threads active 
on my machine. Running JUnit from inside of Eclipse, with MAX_AGE=12, the 
number of active threads never goes above 61, and rarely exceeds 56. 7 
threads is exactly what should be running when there's an active connection
to the server: the base thread, the comm engine thread, and 5 message pool
threads.

I'll check in the changes right away, and you can see if this fixes it for 
you.

	-Mark
-- 
Mark Craig Chu-Carroll,  IBM T.J. Watson Research Center  
*** The Stellation project: Advanced SCM for Collaboration
***		http://www.eclipse.org/stellation
*** Work Email: mcc@xxxxxxxxxxxxxx  ------- Personal Email: markcc@xxxxxxxxxxx