Upgrade from jetty 6.1.24 to 6.1.26 breaks AJP13-connections from apache 2.2.x
Description
Acceptance / Success Criteria
Lucidchart Diagrams
Activity
Benjamin Reed December 6, 2010 at 12:00 PM
I've backed the deps down to 6.1.24 for now, when 6.1.27 comes out we'll give it another shot.
Alexander Hoogerhuis December 3, 2010 at 10:17 AM
No, I don't use remote poller maps. And those I would not connect through AJP anyway (given what I know of them). The GWT stuff seems fine through AJP, only issue was one a while back on limiting the sizeof AJP transfers using an apache config variable.
Benjamin Reed December 3, 2010 at 10:04 AM
Huh, so do the remote poller maps and other GWT stuff work for you? I moved away from AJP because all the GWT apps blew up through it.
Alexander Hoogerhuis December 3, 2010 at 9:59 AM
I've basically never had encoding issues as long as Ive used AJP, where as proxying HTTP around can quickly get you into deep water. Exactly why I've never really got into, as its one of those things that just always worked.
David Hustace December 3, 2010 at 9:57 AM
AJP fixes some encoding issue, then, I can assume? Sorry for playing catchup on that issue.
Jetty 6.1.26 seems to have issues with AJP13-connections, breaking setups that have the web gui through apache, etc.
With 6.1.26 plenty of these crops up:
2010-12-03 04:36:32,845 WARN [4797349@qtp-22937433-18] log: handle failed
java.io.IOException: Bad AJP13 rcv packet: 0x0 expected 0x1234 org.mortbay.jetty.ajp.Ajp13Parser@11de7cb
at org.mortbay.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:276)
at org.mortbay.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:152)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
And the GUI is not able to be displayed.
This is also logged with the jetty project as JETTY-1308.