strategy="ms" apply to the threads handle ms was the default .
In fact there were 2 "lf" and "ms" only ms has been kept.
Using an executor allows you to choose different threads models for the connector threads.
emptySessionPath="true" is gone but you can define the <SessionCookie Path="/"/> in the webapp. (See https://community.jboss.org/message/497671#497671).
redirect-port may refer to port on Apache httpd (front-end)... There is a JIRA for that (AS7-4295).
acceptCount is the backlog now that is fixed to 100.
ConnectionTimeout is soTimeout the default is 60000 ms It could be set via org.apache.coyote.http11.DEFAULT_CONNECTION_TIMEOUT
Many thanks for the response, much appreciated.
Does that mean the executor attribute and connecting max-threads attribute in the thread pool definition is mutually exclusive with the max-connections attribute ?
If acceptCount is now a fixed backlog setting (not exposed?), what does the queue-length element do in the thread pool definition ?
I found the org.apache.coyote.http11.DEFAULT_CONNECTION_TIMEOUT (and also org.apache.coyote.ajp.DEFAULT_CONNECTION_TIMEOUT) system property that you suggested, and noted that
this is working as of JBoss AS 7.1.2.Final (EAP).
I hear what you are saying about the redirect-port, I guess there should be two mutually exclusive attributes then for the correction. Thanks for the jira link.
1 of 1 people found this helpful
I read the code to understand how bounded queue thread-pool handles queue length. Once core threads are all busy (in your case 5), new requests are parked in the queue if space is available in the queue. Only after the queue becomes full, additional threads are created based on the max-threads configuration. So the way this bounded queue thread pool behaves is slightly different from how the old connector behaves.
I tried giving a very small queue length of one and it seems to behave more like the way I wanted. Hope this helps.
I guess I need some definitive clarification. Is the acceptCount/backlog attribute now controlled by the queue-length attribute?
No backlog is fixed to 100 (511 incase of NIO2).