<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'>Do the configuration elements align with the default executor in JBoss Web, which is not the JBoss Threads implementation?<br><br>Andy<br><br><hr id="zwchr"><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Brian Stansberry" <brian.stansberry@redhat.com><br><b>To: </b>jboss-as7-dev@lists.jboss.org<br><b>Sent: </b>Thursday, October 20, 2011 1:24:41 PM<br><b>Subject: </b>Re: [jboss-as7-dev] Controlling Maximum Number of JBoss Web HTTP Threads<br><br>If the web subsystem config is going to change, I'd like to see if it <br>can be made to work the way JCA does[1] -- a config element aligned with <br>the appropriate pool type in the jboss-as-threads.xsd.<br><br>[1] <br>https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/docs/schema/jboss-as-jca_1_0.xsd#L120<br><br>On 10/20/11 2:17 PM, Andrig Miller wrote:<br>> Good thing you looked at the code. I assumed that it impacted the<br>> threads. I guess the defaults have always been big enough for all the<br>> tests I have done then. We should open a JIRA on JBoss Web to add the<br>> maxThreads attribute to the XML schema that goes into domain.xml and<br>> standalone.xml, and have it defined as read-write, so this can be changed.<br>><br>> Andy<br>><br>> ------------------------------------------------------------------------<br>><br>> *From: *"Benjamin Browning" <bbrowning@redhat.com><br>> *To: *"Andrig Miller" <anmiller@redhat.com><br>> *Cc: *"jboss-as7-dev@lists.jboss.org Development"<br>> <jboss-as7-dev@lists.jboss.org><br>> *Sent: *Thursday, October 20, 2011 12:02:56 PM<br>> *Subject: *Re: Controlling Maximum Number of JBoss Web HTTP Threads<br>><br>> The max-connections attribute has no impact on the maximum http<br>> threads. If you look at the code, all it does is set the maximum<br>> poller size and sendfile size for the underlying JIoEndpoint.<br>><br>> To control the threads you either have to use an external executor<br>> or set the maxThreads attribute on the protocol handler (which in<br>> turn sets it on the underlying JIoEndpoint).<br>><br>> Ben<br>><br>> On Oct 20, 2011, at 1:47 PM, Andrig Miller wrote:<br>><br>> Ben,<br>><br>> I think all you have to do is set max-connections="n" to the<br>> number of threads you want. That's what I have been doing, and<br>> based on looking at the running threads through JConsole, it<br>> seems to work just fine. In terms of the executor attribute, and<br>> setting up a pool using JBoss Threads, I have done extensive<br>> testing. I usually see only a small degradation between the two,<br>> like around 1% or so.<br>><br>> Of course, that may vary based on what executor you choose to<br>> use, but I was using the unbounded queue thread thread pool with<br>> good success. I also changed the keepalive time, to keep the<br>> threads around for at least an hour, so to avoid churn in my<br>> testing between executions.<br>><br>> Andy<br>><br>> ------------------------------------------------------------------------<br>><br>> *From:*"Benjamin Browning" <bbrowning@redhat.com<br>> <mailto:bbrowning@redhat.com>><br>> *To:*"Andrig Miller" <anmiller@redhat.com<br>> <mailto:anmiller@redhat.com>><br>> *Cc:*"jboss-as7-dev@lists.jboss.org<br>> <mailto:jboss-as7-dev@lists.jboss.org>Development"<br>> <jboss-as7-dev@lists.jboss.org<br>> <mailto:jboss-as7-dev@lists.jboss.org>><br>> *Sent:*Thursday, October 20, 2011 10:32:01 AM<br>> *Subject:*Controlling Maximum Number of JBoss Web HTTP Threads<br>><br>> I split this thread off from "Two thread pools section in<br>> management API" since it's not directly related.<br>><br>> In my testing I was never able to create an executor for<br>> JBoss Web that didn't have dismal performance. Since<br>> TorqueBox needs to be able to easily control the maximum<br>> number of http threads we've written a simple service that<br>> reads a system property and sets the http connector's<br>> protocol handler's maxThreads. This works great and doesn't<br>> incur the performance hit of using a separate executor. If<br>> there's interest, we could submit a patch upstream to accept<br>> a max-threads attribute on the connector definitions.<br>><br>> Ben<br>><br>> On Oct 20, 2011, at 12:15 PM, Andrig Miller wrote:<br>><br>> One thing that I have found with playing around with the<br>> various subsystems, is JBoss Web. JBoss Web doesn't<br>> expose a thread pool configuration, just a single<br>> attribute called max-connections. It also then has an<br>> "executor" attribute, which just takes a thread pool<br>> name from the JBoss Threads configuration.<br>><br>> So, this one is inconsistent with the other subsystems,<br>> and I'm not sure if it should be changed to be<br>> consistent or not, since the default doesn't use JBoss<br>> Threads. This would also complicate any "global" view in<br>> the console.<br>><br>> Andy<br>><br>><br>><br>><br>><br>><br>><br>><br>> _______________________________________________<br>> jboss-as7-dev mailing list<br>> jboss-as7-dev@lists.jboss.org<br>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<br><br><br>-- <br>Brian Stansberry<br>Principal Software Engineer<br>JBoss by Red Hat<br>_______________________________________________<br>jboss-as7-dev mailing list<br>jboss-as7-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<br></blockquote><br></div></body></html>