[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-348) DefaultMCMPHandler can't handle chunked-encoding

[Gregory Lardiere (JIRA)]

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

Gregory Lardiere commented on MODCLUSTER-348:
---------------------------------------------

It's the response which is chunked-encoded, not the request.
Apache is perfectly right to return a chunked-encoded response because the request is sent as HTTP/1.1.
The problem is that DefaultMCMPHandler doesn't parse this response correctly.
As there is no Content-Length, the HTTP body is not consumed and will be break the next response.
Please look at the stacktraces in the log file.

                
> DefaultMCMPHandler can't handle chunked-encoding
> ------------------------------------------------
>
>                 Key: MODCLUSTER-348
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-348
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04
>         Environment: Windows Server 2008
> JBoss EAP 5.1.0
> EWS 1.0.1
>            Reporter: Gregory Lardiere
>            Assignee: Jean-Frederic Clere
>         Attachments: chunked.log
>
>
> DefaultMCMPHandler send MCMP requests to mod_manager with HTTP version 1.1, but it can't understand chunked-encoded responses. Chunked encoding is mandatory in HTTP 1.1 (RFC2616 3.6.1).
> With lots of nodes, contexts and aliases, the INFO command can return a chunked-encoded response. Then, every STATUS command will fail with a NumberFormatException (cf log).

--
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