[yves.p]

I but "SetEnv force-response-1.0" in my httpd.conf but it changed nothing. HTTPD still response with HTTP/1.1 if the request was HTTP/1.1, explanation here.

INFO / HTTP/1.1
Host: jsplb01w.uyellow.yellowcorp.test:80
Content-Length: 0
User-Agent: ClusterListener/1.0
Connection: Keep-Alive

HTTP/1.1 200 OK
Date: Wed, 21 Dec 2011 18:30:09 GMT
Server: Apache
Vary: Accept-Encoding
Keep-Alive: timeout=10
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/plain 
1f5c
Node: [1],Name: sylber_w_01,Balancer: sylber,LBGroup: ,Host: 10.32.35.127,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10,Ping: 10,Smax: 61,Ttl: 60,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 93
Node: [2],Name: dfs_import_w_01,Balancer: dfsimport,LB
...

[yves.p]

I tried to set "SetEnv downgrade-1.0" and the exception is gone. downgrade-1.0 means that httpd still responds with HTTP/1.1 but doesn't use the 1.1 features, so chunking is turned off.

[rhusar]

Thank for the update and info, I am glad it worked. This should be mentioned in the docs or fix the parsing code.

I guess the question remains why is the AS using HTTP/1.1 and not 1.0.

Rado

PS: https://issues.jboss.org/browse/MODCLUSTER-201

[joaocunhalopes]

The web connector is defined as HTTP1.1 on the AS.

Please take a look at server.xml in jbossweb.sar:

      <!-- A HTTP/1.1 Connector on port 8080 -->

      <Connector protocol="HTTP/1.1" port="8080" address="${jboss.bind.address}"

               connectionTimeout="20000" redirectPort="8443" />

[yves.p]

Thank you for fixing this! I will finally be able to upgrade!

JIRA: https://issues.jboss.org/browse/MODCLUSTER-267

[rhusar]

Yves, you should try the 1.2 (beta4 with the fix) and give feedback then ;-)

Cheers