You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Peter Royal <pr...@apache.org> on 2003/06/12 16:39:32 UTC
[event] Multiple TPCThreadManagers in a JVM
I'm curious if anyone has any experience with multiple TPCThreadManager
instances inside of a single JVM?
I have three instances at the moment, one for event management of my
own, and two others that embedded fortress containers spawn.
What I am noticing, is that frequently, on a 1.4.1_02 JVM under Linux,
my initial TPCThreadManager's monitoring thread will quit right as
Fortress' TPCThreadManager is created.
I just saw that Berin committed some fixes to TPCThreadManager wrt
maximum number of threads for the manager, I'll test those out shortly
to see if that may resolve my problem.
-pete
--
peter royal -> proyal@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [event] Multiple TPCThreadManagers in a JVM
Posted by Peter Royal <pr...@apache.org>.
On Thursday, June 12, 2003, at 10:46 AM, Berin Loritsch wrote:
> The FortressConfig class allows you to pass in your own
> ThreadManager. I highly recommend that you do so when
> you have multiple Fortress containers.
It only allowed the passing in of a Sink before, updated to allow
ThreadManager too now.
-pete
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [event] Multiple TPCThreadManagers in a JVM
Posted by Peter Royal <pr...@apache.org>.
On Thursday, June 12, 2003, at 10:46 AM, Berin Loritsch wrote:
> The FortressConfig class allows you to pass in your own
> ThreadManager. I highly recommend that you do so when
> you have multiple Fortress containers.
Ah, good :) I'll upgrade.
And upon further investigation, it appears that my problem is due to
the Executor blocking because there are no threads available, even when
it appears that the last thread gotten from the pool has been
returned.. very strange.
-pete
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: [event] Multiple TPCThreadManagers in a JVM
Posted by Berin Loritsch <bl...@apache.org>.
The FortressConfig class allows you to pass in your own
ThreadManager. I highly recommend that you do so when
you have multiple Fortress containers.
> -----Original Message-----
> From: Peter Royal [mailto:proyal@apache.org]
> Sent: Thursday, June 12, 2003 10:40 AM
> To: Avalon List
> Subject: [event] Multiple TPCThreadManagers in a JVM
>
>
> I'm curious if anyone has any experience with multiple
> TPCThreadManager
> instances inside of a single JVM?
>
> I have three instances at the moment, one for event management of my
> own, and two others that embedded fortress containers spawn.
>
> What I am noticing, is that frequently, on a 1.4.1_02 JVM
> under Linux,
> my initial TPCThreadManager's monitoring thread will quit right as
> Fortress' TPCThreadManager is created.
>
> I just saw that Berin committed some fixes to TPCThreadManager wrt
> maximum number of threads for the manager, I'll test those
> out shortly
> to see if that may resolve my problem.
> -pete
>
> --
> peter royal -> proyal@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org