[jboss-jira] [JBoss JIRA] (AS7-5980) HTTP connector has missing configuration
Paul Hinds (JIRA)
jira-events at lists.jboss.org
Tue Nov 20 07:34:22 EST 2012
[ https://issues.jboss.org/browse/AS7-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735675#comment-12735675 ]
Paul Hinds commented on AS7-5980:
---------------------------------
KeepAlive timeout is not configurable as a system property, that's the main problem. So we have to disable keepalive completely with "max keep alive requests" which is a system property.
The timeout is hardcoded to 15 seconds in the JBossAS7, at least documentation indicates it is not configurable, and according to this thread too https://community.jboss.org/message/777236#777236.
Having the option as a system property would probably suffice in this case. It means we can't tune it per connector which is a pain, but better than a "no fix".
> HTTP connector has missing configuration
> ----------------------------------------
>
> Key: AS7-5980
> URL: https://issues.jboss.org/browse/AS7-5980
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Web
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Paul Hinds
> Assignee: Remy Maucherat
>
> We have an application that is using the JBoss HTTP connector without Apache in front. Because keep-alive timeout is not configurable we have to accept defaults which means for a request that takes 10ms to complete we seem to dedicate a thread for 15 seconds. It is impossible to balance performance with concurrency without this option.
> Other options are missing from JBossAs7 that are required for performance.
> max keep alive requests
> tcp no delay
> max http header size
> connection timeout
> compression
> These should be configurable in the connector XML having some parameters available via system properties is inconvenient.
> max header size and keep alive timeout are the showstoppers for our use of JBoss.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list