Re: [jboss-as7-dev] New openshift resource issue

During startup, it seems that deployment of multiple apps is using a lot of threads due to processing of the associated services. I'm working on identifying where all the uses are coming from. If you know there is a hard limit to the number of threads that can be created, it would be good to be able to know the server configuration will not exceed that. On 7/20/11 3:51 AM, Emanuel Muckenhuber wrote: > I'm afraid that the current thread-pool configuration is not really > consistent. We plan to remove the threads subsystem and move the thread > pool configuration directly in each subsystem where they are used. At > least that's the last i heard of. > > I assume we would also need add a thread pool configuration for 'system' > (non subsystem specific) usages as well in order to be able to address > the resource issue Scott described. > > On 07/20/2011 09:03 AM, Heiko Braun wrote: >> Good point. >> I was thinking about this today as well. >> Basically you cannot tell what thread pool each subsystem relies on. >> Ideally they would be referencing thread pools by it's logical name through the configuration. >> >> Ike >> >> On Jul 19, 2011, at 10:20 PM, Scott Stark wrote: >> >>> Right now there are no subsystems referring to a thread pool in the >>> threads subsystem. >>> >>> At a minimum, there needs to be a sample standalone.xml configuration >>> that is tested that illustrates how to do this if we are not going to do >>> this by default. >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev