You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2004/07/29 06:49:58 UTC
Migration ... change for Thread Pool
Stephen,
In branch_2_1_fcs. we use org.apache.james.util.thread.DefaultThreadManager
because the Avalon code was badly broken. Our code is basically a fixed
version of Avalon's code.
Leif Mortenson did work on ResourceLimitingThreadManger, which should be
able to replace
org.apache.avalon.cornerstone.blocks.threads.DefaultThreadManager and our
implementation class.
Unfortunately,
http://avalon.apache.org/api/org/apache/avalon/excalibur/thread/impl/Resourc
eLimitingThreadPool.html no longer works,
http://avalon.apache.org/planet/components/threads.html is useless, and even
when I found the javadocs, these classes are missing. I assume that this is
still part of the repair work Aaron and others are still working on. Either
that or I am simply looking in the wrong place.
Can you tell me where they are, what the configuration elements are, etc.?
I am trying to get the branches merged, and this is one of my outstanding
issues. It appears that the james-assembly.xml should be changed to
reference Leif's class.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: Migration ... change for Thread Pool
Posted by Stephen McConnell <mc...@apache.org>.
> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com]
> 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 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 Excalibur, but the installable component,
> ResourceLimitingThreadManger, is a Cornerstone block.
So we are taking about the following packages:
* excalibut-thread-api-2.0.0
* excalibur-thread-impl-2.0.0
* cornerstone-thread-api-2.0.0
* cornerstone-thread-impl-2.0.0
This basically translates to the Excalibur packages because the cornerstone
stuff is a light-weight wrapper around Excalibur-thread.
> The docs for the pool are at
> http://excalibur.apache.org/apidocs/org/apache/avalon/excalibur/thread/imp
> l/
> ResourceLimitingThreadPool.html, but I cannot find the active Cornerstone
> docs.
Progress on docs was recently cutback due to some discussion concerning
framework semantics. However, if you want to get the docs for cornerstone
threads just do the following:
1. checkout Avalon/trunk
2 from the checkjout directory
$ ant setup
$ ant
3. cd down to planet/cornerstone/threads/impl
$ ant javadoc
The javadoc output will be aggregated under ${magic.home}/docs which should
default to ${user.home}/.magic/docs if your running on defaults. The docs
should include all transitive dependencies so you should have a complete
picture of where things are.
> For that matter, I am having trouble finding the active Cornerstone
> sources.
The answer is avalon/trunk/planet/cornerstone/
> Where are they other than in the cvs-migration-snapshot
> (http://svn.apache.org/repos/asf/avalon/cvs-migration-snapshot/avalon-
> compon
> ents/cornerstone/threads/impl/src/java/org/apache/avalon/cornerstone/block
> s/
> threads/)?
See above.
> > James MAIN HEAD is working properly against the last release
> > of Excalibur Thread 2.0.0 and the corresponding Cornerstone
> > Thread package.
>
> I doubt it. The default code doesn't implement hard limits on resource
> usage, which is what we want. So although it might appear to be working
> properly, it isn't behaving as we want.
The best thing to do is to submit as issue here:
http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10532
> > Concerning your issues with Excalibur Thread - I guess this should be
> > directed to the Excalibur Project.
>
> Not unless they have taken over Cornerstone, too.
That depends where your problem is - James has direct dependencies on
Excalibur and uses Cornerstone threads as well. Excalibur is the center for
Excalibur issues; Avalon is the center for Cornerstone issue. If there is a
cornerstone issue - can you post the issue to the above url and we can take
it from there.
Cheers, Stephen.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: Migration ... change for Thread Pool
Posted by "Noel J. Bergman" <no...@devtech.com>.
> 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 Excalibur, but the installable component,
ResourceLimitingThreadManger, is a Cornerstone block.
The docs for the pool are at
http://excalibur.apache.org/apidocs/org/apache/avalon/excalibur/thread/impl/
ResourceLimitingThreadPool.html, but I cannot find the active Cornerstone
docs. For that matter, I am having trouble finding the active Cornerstone
sources. Where are they other than in the cvs-migration-snapshot
(http://svn.apache.org/repos/asf/avalon/cvs-migration-snapshot/avalon-compon
ents/cornerstone/threads/impl/src/java/org/apache/avalon/cornerstone/blocks/
threads/)?
> James MAIN HEAD is working properly against the last release
> of Excalibur Thread 2.0.0 and the corresponding Cornerstone
> Thread package.
I doubt it. The default code doesn't implement hard limits on resource
usage, which is what we want. So although it might appear to be working
properly, it isn't behaving as we want.
> Concerning your issues with Excalibur Thread - I guess this should be
> directed to the Excalibur Project.
Not unless they have taken over Cornerstone, too.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: Migration ... change for Thread Pool
Posted by "Noel J. Bergman" <no...@devtech.com>.
> 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 Excalibur, but the installable component,
ResourceLimitingThreadManger, is a Cornerstone block.
The docs for the pool are at
http://excalibur.apache.org/apidocs/org/apache/avalon/excalibur/thread/impl/
ResourceLimitingThreadPool.html, but I cannot find the active Cornerstone
docs. For that matter, I am having trouble finding the active Cornerstone
sources. Where are they other than in the cvs-migration-snapshot
(http://svn.apache.org/repos/asf/avalon/cvs-migration-snapshot/avalon-compon
ents/cornerstone/threads/impl/src/java/org/apache/avalon/cornerstone/blocks/
threads/)?
> James MAIN HEAD is working properly against the last release
> of Excalibur Thread 2.0.0 and the corresponding Cornerstone
> Thread package.
I doubt it. The default code doesn't implement hard limits on resource
usage, which is what we want. So although it might appear to be working
properly, it isn't behaving as we want.
> Concerning your issues with Excalibur Thread - I guess this should be
> directed to the Excalibur Project.
Not unless they have taken over Cornerstone, too.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Migration ... change for Thread Pool
Posted by Stephen McConnell <mc...@apache.org>.
> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com]
> Sent: Thursday, July 29, 2004 06:50
> To: Stephen McConnell
> Cc: James-Dev Mailing List; dev@avalon.apache.org
> Subject: Migration ... change for Thread Pool
>
> Stephen,
>
> In branch_2_1_fcs. we use
> org.apache.james.util.thread.DefaultThreadManager
> because the Avalon code was badly broken. Our code is basically a fixed
> version of Avalon's code.
Are you referring to the Excalibur Thread package? If so, which version are
your referring to? James MAIN HEAD is working properly against the last
release of Excalibur Thread 2.0.0 and the corresponding Cornerstone Thread
package. I have also tested this locally and can assure you that nothing
appears to be broken and that James is doing its stuff.
Concerning your issues with Excalibur Thread - I guess this should be
directed to the Excalibur Project. There is also the JIRA for posting
issues.
http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10428
Stephen.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: Migration ... change for Thread Pool
Posted by Stephen McConnell <mc...@apache.org>.
> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com]
> Sent: Thursday, July 29, 2004 06:50
> To: Stephen McConnell
> Cc: James-Dev Mailing List; dev@avalon.apache.org
> Subject: Migration ... change for Thread Pool
>
> Stephen,
>
> In branch_2_1_fcs. we use
> org.apache.james.util.thread.DefaultThreadManager
> because the Avalon code was badly broken. Our code is basically a fixed
> version of Avalon's code.
Are you referring to the Excalibur Thread package? If so, which version are
your referring to? James MAIN HEAD is working properly against the last
release of Excalibur Thread 2.0.0 and the corresponding Cornerstone Thread
package. I have also tested this locally and can assure you that nothing
appears to be broken and that James is doing its stuff.
Concerning your issues with Excalibur Thread - I guess this should be
directed to the Excalibur Project. There is also the JIRA for posting
issues.
http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10428
Stephen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org