> -Original Message-
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: donderdag 29 juli 2004 18:44
> To: James Developers List
> Subject: RE: Migration ... change for Thread Pool
>
> > 1) Is it an option to use the Apache Commons Thread Pool?
> >
> -Original Message-
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 29, 2004 16:42
> To: Avalon Developers List; 'James Developers List'
> Subject: RE: Migration ... change for Thread Pool
>
> > Are you referring to the E
> 1) Is it an option to use the Apache Commons Thread Pool?
>It is stable, widely used and highly configurable.
Someone would have to write a block for it.
> I would like to be able to configure my thread pool so it
> blocks (with a time-out) until a new thread is available,
> so more mail wi
Developers List; 'James Developers List'
Subject: RE: Migration ... change for Thread Pool
> Are you referring to the Excalibur Thread package?
Only partially. To quote you from about 5 minutes ago, " The cornerstone
components (in most cases) handle the adaptation between
> Are you referring to the Excalibur Thread package?
Only partially. To quote you from about 5 minutes ago, " The cornerstone
components (in most cases) handle the adaptation between the Phoenix/Merlin
component model and the Excalibur utilities." In this case,
ResourceLimitingThreadPool is in E
> -Original Message-
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 29, 2004 06:50
> To: Stephen McConnell
> Cc: James-Dev Mailing List; [EMAIL PROTECTED]
> Subject: Migration ... change for Thread Pool
>
> Stephen,
>
> In branch_2_1_fcs. we use
> org.apache.ja
