[
https://issues.jboss.org/browse/AS7-4226?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat resolved AS7-4226.
---------------------------------
Resolution: Won't Fix
Yes, the check is good enough as is. There's no reason to mention this in docs or faqs
since this is about a HTTP connection timeout, where 5s is already too short to be
practical.
Async servlet operation timeout check should run more frequently
----------------------------------------------------------------
Key: AS7-4226
URL:
https://issues.jboss.org/browse/AS7-4226
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.1.Final
Reporter: Martin Kouba
Assignee: Remy Maucherat
Priority: Minor
The async servlet operation timeout check is run approx. every ten seconds. This is not
very practical/precise assuming the timeout is specified in milliseconds ->
{{javax.servlet.AsyncContext.setTimeout(long)}}.
Not completely sure about the exact time - 10s occures in my simple CDI TCK test).
Looking at {{org.apache.tomcat.util.net.JIoEndpoint#Poller.maintain()}} five seconds is
hard coded minimum: "Maintain runs at most once every 5s".
I suppose this is intentional and due to performance reasons. If so it should be FAQed or
mentioned in docs. Otherwise it should be fixed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira