Re: HotSpot crashed on Linux

Juha Laiho wrote:
> Roedy Green <see_website@[EMAIL PROTECTED]
> said:
> 
>>On the other paw, only one nugget of work can run at a time with a
>>single Timer.  
> 
> 
> So, would a ThreadPool assigned as worker threads for a Timer be the
> "correct solution" for this? This of course leaves the issue of
> pool sizing, but I think in most cases it shouldn't be too hard to
> find some ballpark figure; 10, 50, ... . Still much less than the
> 4500 or so that the OP started with.

... with the timer simply queueing work to one of the worker threads. 
I've seen this (successfully) done on projects - means you only need one 
timer object as all its thread does is invoke methods on the worker
threads.

(I really, really hate the built in timer class - it has other features 
(associated with TimerTask cancellation) that can lead the unwary to 
OutOfMemory exceptions if they aren't careful.  The 1.5 and on "fix" 
feels like a nasty hack to me...

Dave