Details
Closed
Major
Description
It seems that after upgrading our Sonar to 2.12 (running as a standalone service) it no longer works with mod_proxy_ajp in our Apache server.
Each request will result in a log line like this in sonar.log:
INFO | jvm 1 | 2011/12/06 10:24:37 | 2011-12-06 10:24:37.246:WARN::handle failed INFO | jvm 1 | 2011/12/06 10:24:37 | java.io.IOException: Bad AJP13 rcv packet: 0x0 expected 0x1234 org.mortbay.jetty.ajp.Ajp13Parser@bbec16 INFO | jvm 1 | 2011/12/06 10:24:37 | at org.mortbay.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:276) INFO | jvm 1 | 2011/12/06 10:24:37 | at org.mortbay.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:152) INFO | jvm 1 | 2011/12/06 10:24:37 | at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) INFO | jvm 1 | 2011/12/06 10:24:37 | at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228) INFO | jvm 1 | 2011/12/06 10:24:37 | at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Downgrading the Jetty binaries in Sonar to 6.1.24 (from Sonar 2.11) seems to have fixed that issue.
Issue Links
- depends upon
-
JETTY-1308
AJP13 connections broken with 6.1.26
-
