Hi,

>> Also, I think org.apache.avalon.cornerstone.blocks.connection.Connection
>> class has to be modified in case of ResourceLimitingThreadManager...

>In what way?

Simply: creating of connection handler has to be moved to be inside internal
ConnectionRunner class. Why? If using resource limiting pool and number of
threads is exceeded it shouldn't create handler at all. Now it creates but
doesn't call handle connection which doesn't make any sense from my point of
view.

Andrei


----- Original Message -----
From: "Peter Donald" <[EMAIL PROTECTED]>
To: "Avalon-Phoenix Developers List" <[email protected]>
Sent: Wednesday, July 10, 2002 2:03 PM
Subject: Re: Re: ResourceLimitingThreadPool support in cornerstone?


On Tue, 9 Jul 2002 22:06, Andrei Ivanov wrote:
> This is what I am working on now. So far I came across with simple
problem.
> I have phoenix based server application: usual connection handler etc.
When
> I was using DefaultThreadManager (DefaultThreadPool) I had sometime
> situations when server was just creating new threads (hundreds of them).
> After looking deeply into this problem I found mentioned lack of support
of
> ResourceLimitingThreadPool in cornerstone. So I implemented new
> ResourceLimitingThreadManager and now testing it.

kool!

> The problem is that when
> number of threads reached its maximum (so that no new connection handlers
> are created) I can not stop Phoenix without following exception (see PS).

hmm. I will look into that. Could you lodge a bug on Bugzilla?

> Also, I think org.apache.avalon.cornerstone.blocks.connection.Connection
> class has to be modified in case of ResourceLimitingThreadManager...

In what way?

--
Cheers,

Peter Donald
-------------------------------------------------------------
|  Egoism is the drug that soothes the pain of stupidity.   |
-------------------------------------------------------------


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]
che.org>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to