java.io.IOException: AJP13 packet (8634bytes) too large for buffer

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Ajp13Parser IOException
    via by david.seymore,
  • We are running jenkins as a standalone server using a war file. We have enabled AJP13 port so Apache (installed on the same server) can serve it as a proxy. Jenkins runs fine but intermittently throws "Bad AJP13 rcv packet" IOExceptions and stops working. On the browser apache says, system temporarily available. I could connect to jenkins just fine by hitting direct https port it is running. Here is exception: ============================ INFO: Jenkins is fully up and running Apr 08, 2014 5:34:58 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: handle failed? java.io.IOException: Bad AJP13 rcv packet: 0x5f2e expected 0x1234 org.eclipse.jetty.ajp.Ajp13Parser@17ac5bd at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:276) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:158) at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) =============================== Apache AJP config: ========================== ProxyPass /jenkins ajp://localhost:9091/jenkins ProxyPassReverse /jenkins ajp://localhost:9091/jenkins ProxyRequests Off ========================== Any help is appreciated.
    via by divyesh vora,
  • We are running jenkins as a standalone server using a war file. We have enabled AJP13 port so Apache (installed on the same server) can serve it as a proxy. Jenkins runs fine but intermittently throws "Bad AJP13 rcv packet" IOExceptions and stops working. On the browser apache says, system temporarily available. I could connect to jenkins just fine by hitting direct https port it is running. Here is exception: ============================ INFO: Jenkins is fully up and running Apr 08, 2014 5:34:58 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: handle failed? java.io.IOException: Bad AJP13 rcv packet: 0x5f2e expected 0x1234 org.eclipse.jetty.ajp.Ajp13Parser@17ac5bd at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:276) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:158) at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) =============================== Apache AJP config: ========================== ProxyPass /jenkins ajp://localhost:9091/jenkins ProxyPassReverse /jenkins ajp://localhost:9091/jenkins ProxyRequests Off ========================== Any help is appreciated.
    via by divyesh vora,
  • Trying to uppload an new artifact, clicking on upload button the following message appears in browser: Bad Gateway The proxy server received an invalid response from an upstream server. Access to artifactory is thru AJP with frontend apache httpd server Trying this on jetty http port directly works In consoleout.log the is the following message: 2010-06-17 14:33:45.368:WARN::handle failed? java.io.IOException: FULL at org.eclipse.jetty.ajp.Ajp13Parser.fill(Ajp13Parser.java:199) at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:553) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:156) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:417) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:250) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) 2010-06-17 14:33:45.478:WARN::handle failed? java.io.IOException: FULL at org.eclipse.jetty.ajp.Ajp13Parser.fill(Ajp13Parser.java:199) at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:553) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:156) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:417) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:250) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) 2010-06-17 14:33:45.589:WARN::handle failed? java.io.IOException: FULL at org.eclipse.jetty.ajp.Ajp13Parser.fill(Ajp13Parser.java:199) at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:553) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:156) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:417) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:250) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) 2010-06-17 14:33:45.730:WARN::handle failed? java.io.IOException: FULL at org.eclipse.jetty.ajp.Ajp13Parser.fill(Ajp13Parser.java:199) at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:553) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:156) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:417) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:250) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)
    via by Markus Pohle,
  • When I try to create a new build plan through the web interface I get this error. For us it is important to use the AJP protocol as we use it for all other Atlassian products. We use AJP authentication for Fisheye and rely on setting the REMOTE_USER property for all other products. Customize org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint@d2f353 (GET /builds/s/2302/1/3.3.1/_/download/batch/com.atlassian.auiplugin:ajs/images/icons/aui-message-icon-sprite.png)@9773284 org.eclipse.jetty.ajp.Ajp13Request@9520e4 2011-02-25 18:15:17.780:WARN::handle failed? java.io.IOException: FULL at org.eclipse.jetty.ajp.Ajp13Parser.fill(Ajp13Parser.java:200) at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:566) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:157) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:426) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:241) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:450) at java.lang.Thread.run(Thread.java:619) 2011-02-25 18:15:17.889:WARN::handle failed? java.io.IOException: FULL at org.eclipse.jetty.ajp.Ajp13Parser.fill(Ajp13Parser.java:200) at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:566) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:157) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:426) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:241) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:450) at java.lang.Thread.run(Thread.java:619)
    via by Daniel Varela Santoalla,
  • 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: {code} [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) {code} Jetty log: {code} 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) {code}
    via by Martin Barrs,
  • Trying to uppload an new artifact, clicking on upload button the following message appears in browser: Bad Gateway The proxy server received an invalid response from an upstream server. Access to artifactory is thru AJP with frontend apache httpd server Trying this on jetty http port directly works In consoleout.log the is the following message: 2010-06-17 14:33:45.368:WARN::handle failed? java.io.IOException: FULL at org.eclipse.jetty.ajp.Ajp13Parser.fill(Ajp13Parser.java:199) at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:553) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:156) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:417) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:250) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) 2010-06-17 14:33:45.478:WARN::handle failed? java.io.IOException: FULL at org.eclipse.jetty.ajp.Ajp13Parser.fill(Ajp13Parser.java:199) at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:553) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:156) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:417) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:250) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) 2010-06-17 14:33:45.589:WARN::handle failed? java.io.IOException: FULL at org.eclipse.jetty.ajp.Ajp13Parser.fill(Ajp13Parser.java:199) at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:553) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:156) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:417) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:250) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) 2010-06-17 14:33:45.730:WARN::handle failed? java.io.IOException: FULL at org.eclipse.jetty.ajp.Ajp13Parser.fill(Ajp13Parser.java:199) at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:553) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:156) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:417) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:250) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)
    via by Markus Pohle,
    • java.io.IOException: AJP13 packet (8634bytes) too large for buffer at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:281) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:158) at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:722)

    Users with the same issue

    Unknown visitor1 times, last one,