[
https://issues.jboss.org/browse/ARQ-982?page=com.atlassian.jira.plugin.sy...
]
Ste Gr commented on ARQ-982:
----------------------------
In my case the exception occurres because of the header
"X-Arq-Enrichment-Response". The value has a length of 19980 bytes. It consists
of org.jboss.arquillian.warp.shared.ResponsePayload which contains a weld exception
(@Inject failed due to an programm specific exception).
The root cause for this error is the fact, that no boundary check is performed while the
buffer gets filled in org.apache.coyote.http11.InternalOutputBuffer line 698 (jboss web
7.0.13.Final). The whole routine is simply not able to split the send of headers.
Response header size exceeded in Warp test.
-------------------------------------------
Key: ARQ-982
URL:
https://issues.jboss.org/browse/ARQ-982
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha1
Environment: JBoss AS 7.1.1
Reporter: Jakub Narloch
Priority: Critical
Fix For: warp_1.0.0.Alpha2
This can be reproduced in remote JBoss AS 7 by moving in PhaserBasicTest(phaser-ftest
module) the {code}@ArquillianResource URL contextPath;{code} into the ServerAssertion.
This ends in exceeding the maximum size of the response header:
{code}
16:55:05,703 ERROR [org.apache.catalina.connector.CoyoteAdapter] (http--127.0.0.
1-8080-1) An exception or error occurred in the container during the request processing:
java.lang.ArrayIndexOutOfBoundsException: 8192
at
org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffer.java:698)
[jbossweb-7.0.13.Final.jar:]
at
org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffer.java:607)
[jbossweb-7.0.13.Final.jar:]
at
org.apache.coyote.http11.InternalOutputBuffer.sendHeader(InternalOutputBuffer.java:479)
[jbossweb-7.0.13.Final.jar:]
at
org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processor.java:1648)
[jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:998)
[jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.Response.action(Response.java:190)
[jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.Response.sendHeaders(Response.java:390)
[jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:335)
[jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:301)
[jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.Response.finishResponse(Response.java:479)
[jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:395)
[jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.13.Final.jar:]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
[jbossweb 7.0.13.Final.jar:]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
[jbossweb-7.0.13.Final.jar:]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira