[jboss-jira] [JBoss JIRA] (AS7-5980) HTTP connector has missing configuration

[Alex Bloom (JIRA)]

    [ https://issues.jboss.org/browse/AS7-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793316#comment-12793316 ] 

Alex Bloom commented on AS7-5980:
---------------------------------

The current JBoss http connector is not useful for high load environments. Tunable KeepAlive timeout is required, as are all of the other parameters mentioned (and more). This is why all other web servers allow them to be tuned. Did all of these other web server maintainers get it wrong? Apache, nginx, tomcat, glassfish, ... You should send these guys an email to let them know that their implementations are needlessly complex and could be solved with one size fits all defaults like 15s for KeepAlive. I'm sure they would be happy to learn of this wisdom.
                
> 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