[jboss-as7-dev] Two thread pools sections in management API

[Jason Greene]

Right. What happened is we found out that having thread pools be global promotes sharing, which is usually an error since each subsystem needs specific configurations. We were planning on adding a global view that would see all the subsystems' thread pools so the administrator can easily identify which were in use however I don't think it was completed yet. Even though we neat them in the subsystem we still want them to be consistent.

Sent from my iPhone

On Oct 20, 2011, at 5:58 AM, Heiko Braun <hbraun at redhat.com> wrote:

> 
> 
> no, but if possible they should rely on the default schema (xsd) for defining inlined thread pool configurations.
> 
> On Oct 20, 2011, at 12:50 PM, David Bosschaert wrote:
> 
>> It seems that the latter defines pools that are used in 
>> /subsystem=ejb3/service=*
>> Should they not be using thread pools defined in the threads subsystem 
>> instead?
> 
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20111020/7a15fa61/attachment-0001.html