Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-10143

IOExceptions in log file: "Bad AJP13 rcv packet expected 0x1234"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Medium Medium
    • None
    • 3.3.2
    • Installation

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

            [BAM-10143] IOExceptions in log file: "Bad AJP13 rcv packet expected 0x1234"

            James Dumay added a comment -

            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

            James Dumay added a comment - 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

            Brian Topping added a comment -

            I'm also having this issue in Bamboo 3.4.4 with the jar provided here.

            In trying the fix that Martin Barrs added above, I upgraded the Jetty jars to 7.5.4, but between then and now, there is a new call to an old api:

            Exception in thread "main" java.lang.NoSuchMethodError: org.eclipse.jetty.xml.XmlConfiguration.configure(Ljava/lang/Object;)V
	at com.atlassian.bamboo.server.Server.<init>(Server.java:137)
	at com.atlassian.bamboo.server.Server.main(Server.java:47)

            Could someone please please please upgrade the next release of Bamboo to working Jetty jars that are less than a year out of date and without known bugs?

            Brian Topping added a comment - I'm also having this issue in Bamboo 3.4.4 with the jar provided here . In trying the fix that Martin Barrs added above, I upgraded the Jetty jars to 7.5.4, but between then and now, there is a new call to an old api: Exception in thread "main" java.lang.NoSuchMethodError: org.eclipse.jetty.xml.XmlConfiguration.configure(Ljava/lang/ Object ;)V at com.atlassian.bamboo.server.Server.<init>(Server.java:137) at com.atlassian.bamboo.server.Server.main(Server.java:47) Could someone please please please upgrade the next release of Bamboo to working Jetty jars that are less than a year out of date and without known bugs?

            Martin Barrs added a comment -

            I replaced the distributed Jetty files with the complete set of .jars from Jetty 7.5.4, per Jetty issue JETTY-1097.

            Bamboo then works well.

            I beleive the solution to this issue if for Atlassian to update the version of Jetty distributed by Bamboo, and to include the AJP jar.

            Martin Barrs added a comment - I replaced the distributed Jetty files with the complete set of .jars from Jetty 7.5.4, per Jetty issue JETTY-1097. Bamboo then works well. I beleive the solution to this issue if for Atlassian to update the version of Jetty distributed by Bamboo, and to include the AJP jar.

            Martin Barrs added a comment -

            Replaced the Jetty AJP connector with the connector above, and same issue:

            INFO   | jvm 1    | 2011/11/09 13:14:01 | 2011-11-09 13:14:01.002:WARN::handle failed?
INFO   | jvm 1    | 2011/11/09 13:14:01 | java.io.IOException: Bad AJP13 rcv packet: 0x0 expected 0x1234 org.eclipse.jetty.ajp.Ajp13Parser@18761e4d
INFO   | jvm 1    | 2011/11/09 13:14:01 |       at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:273)
INFO   | jvm 1    | 2011/11/09 13:14:01 |       at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:151)
INFO   | jvm 1    | 2011/11/09 13:14:01 |       at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:426)
INFO   | jvm 1    | 2011/11/09 13:14:01 |       at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:241)
INFO   | jvm 1    | 2011/11/09 13:14:01 |       at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:450)
INFO   | jvm 1    | 2011/11/09 13:14:01 |       at java.lang.Thread.run(Thread.java:662)

            Martin Barrs added a comment - Replaced the Jetty AJP connector with the connector above, and same issue: INFO | jvm 1 | 2011/11/09 13:14:01 | 2011-11-09 13:14:01.002:WARN::handle failed? INFO | jvm 1 | 2011/11/09 13:14:01 | java.io.IOException: Bad AJP13 rcv packet: 0x0 expected 0x1234 org.eclipse.jetty.ajp.Ajp13Parser@18761e4d INFO | jvm 1 | 2011/11/09 13:14:01 | at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:273) INFO | jvm 1 | 2011/11/09 13:14:01 | at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:151) INFO | jvm 1 | 2011/11/09 13:14:01 | at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:426) INFO | jvm 1 | 2011/11/09 13:14:01 | at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:241) INFO | jvm 1 | 2011/11/09 13:14:01 | at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:450) INFO | jvm 1 | 2011/11/09 13:14:01 | at java.lang. Thread .run( Thread .java:662)

            Martin Barrs added a comment -

            There was no AJP module in the Bamboo distro - I used the corresponding AJP jar from Jetty.

            Martin Barrs added a comment - There was no AJP module in the Bamboo distro - I used the corresponding AJP jar from Jetty.

            Przemek Bruski added a comment -

            Are you using the AJP module provided by Atlassian ?

            Przemek Bruski added a comment - Are you using the AJP module provided by Atlassian ?

              Unassigned Unassigned
              06ef8487e673 Martin Barrs
              Affected customers:
              2 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: