You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Paul Hammant <Pa...@thoughtworks.net> on 2003/05/18 11:54:26 UTC
Re: ThreadPool(Manager) with hard limits
Noel,
You still could chuck a patch at us dude ;-) Just from HEAD of relevent
modules.
- Paul
>>Chuck a patch back at us dude - into excalibur-pool & excalibur-thread ?
>>
>>
>
>You don't want my code. I just cloned ancient versions of your code, half
>of them out of attics, to coggle together a ThreadManager for the version of
>Phoenix we are shipping with James v2. When there finally is a new RELEASE
>of the Avalon packages suitable for James, I will want to kill off our
>package.
>
>see:
>http://cvs.apache.org/viewcvs/jakarta-james/src/java/org/apache/james/util/t
>hread/?only_with_tag=branch_2_1_fcs.
>
>------
>Instructions:
>
>All that you do is clone DefaultThreadPool and create
>HardResourceThreadPool. Change the instantiation from
>SoftResourceLimitingPool to HardResourceLimitingPool. MAKE SURE that you
>copy the nasty hack that I had to add, or fix the inconsistent
>initialization of your pool classes. Then clone DefaultThreadManager to
>create HardResourceThreadManager, and have it instantiate a
>HardResourceThreadPool instead of a DefaultThreadPool.
>
>Since you will be working in your own packages, and therefore won't run into
>the package permission problems, you won't need the other classes I had to
>clone. If you take the easy way out, this is 5 minutes worth of work, and
>that's only if you're using vi. In Emacs, it would be 60 seconds, tops.
>------
>
>Ideally, all of that could be avoided by changing DefaultThreadPool and
>DefaultThreadManager to be configurable to the particular type of underlying
>resource pool. But I have enough code to work on.
>
> --- Noel
>
>
--
http://www.thoughtworks.com -> The art of heavy lifting.
Home for many Agile-practicing, Open Source activists...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: ThreadPool(Manager) with hard limits
Posted by Leif Mortenson <le...@tanukisoftware.com>.
Noel J. Bergman wrote:
>>You still could chuck a patch at us dude ;-) Just from HEAD of relevent
>>modules.
>>
>>
>
>If Leif Mortenson's ResourceLimitingThreadManager does what it claims (if
>not, I'll assume that it is just a bug), then that is the right solution.
>Mine was just a hack. When the new Avalon Release cycle is finished, we can
>just adopt his new manager into James.
>
Ok let me know if there are any problems. Cc me directly. It is hard
to keep up
with all the traffic on the list and some messages get by me when I get
busy.
I miss the phoenix, etc lists.
Cheers,
Leif
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: ThreadPool(Manager) with hard limits
Posted by "Noel J. Bergman" <no...@devtech.com>.
> You still could chuck a patch at us dude ;-) Just from HEAD of relevent
> modules.
If Leif Mortenson's ResourceLimitingThreadManager does what it claims (if
not, I'll assume that it is just a bug), then that is the right solution.
Mine was just a hack. When the new Avalon Release cycle is finished, we can
just adopt his new manager into James.
[Thanks, Leif. :-)]
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org