-
Bug
-
Resolution: Obsolete
-
Medium
-
None
-
3.3.2
-
Linux x64, Apache 2.2 + mod_proxy_ajp, Jetty 7.2.1 + AJP
Proxying Bamboo using AJP with mod_proxy_ajp is inconsistent, timing out pages or generating on page errors, with the following log file errors -
HTTPD log:
[Tue Nov 08 17:02:45 2011] [error] (70014)End of file found: ajp_ilink_receive() can't receive header
[Tue Nov 08 17:02:45 2011] [error] ajp_read_header: ajp_ilink_receive failed
[Tue Nov 08 17:02:45 2011] [error] (120006)APR does not understand this error code: proxy: read response failed from 127.0.0.1:8086 (localhost)
Jetty log:
INFO | jvm 1 | 2011/11/08 17:00:15 | Customize org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint@5efefc32 (GET /bamboo/rest/api/latest/server?_=1320800414950)@656075868 org.eclipse.jetty.ajp.Ajp13Request@271aec5c INFO | jvm 1 | 2011/11/08 17:00:45 | 2011-11-08 17:00:45.191:WARN::handle failed? INFO | jvm 1 | 2011/11/08 17:00:45 | java.io.IOException: Bad AJP13 rcv packet: 0x0 expected 0x1234 org.eclipse.jetty.ajp.Aj p13Parser@4d74bd22 INFO | jvm 1 | 2011/11/08 17:00:45 | at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:273) INFO | jvm 1 | 2011/11/08 17:00:45 | at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:151) INFO | jvm 1 | 2011/11/08 17:00:45 | at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:426) INFO | jvm 1 | 2011/11/08 17:00:45 | at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConne ctor.java:241) INFO | jvm 1 | 2011/11/08 17:00:45 | at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:450 ) INFO | jvm 1 | 2011/11/08 17:00:45 | at java.lang.Thread.run(Thread.java:662)
- relates to
-
BAM-11371 Upgrade Jetty to 7.6.2
- Closed
[BAM-10143] IOExceptions in log file: "Bad AJP13 rcv packet expected 0x1234"
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1436488 ] | New: JAC Bug Workflow v3 [ 3384168 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1417957 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1436488 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 606687 ] | New: Bamboo Workflow 2016 v1 [ 1417957 ] |
Workflow | Original: Bamboo Workflow 2014 [ 594139 ] | New: Bamboo Workflow 2014 v2 [ 606687 ] |
Workflow | Original: Bamboo Workflow 2010 [ 353106 ] | New: Bamboo Workflow 2014 [ 594139 ] |
Resolution | New: Obsolete [ 11 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Labels | New: jetty |
Component/s | New: Installation [ 11430 ] | |
Component/s | Original: Bamboo Release [ 12254 ] | |
Fix Version/s | Original: Milestone Discoveries [ 20791 ] |
Hi there,
In Bamboo 5.1, we've switched from Jetty to Tomcat which makes this issue obsolete.
If you have any queries, please do not hesitate to get in touch with Atlassian Support.
Thanks
James