[MAGNOLIA-3912] Jetty is failing because of increased header size Created: 12/Dec/11  Updated: 25/May/12  Resolved: 23/May/12

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.5
Fix Version/s: 4.5.3

Type: Bug Priority: Major
Reporter: Daniel Lipp Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLEE-230 CLONE -Jetty is failing because of in... Closed
dependency
is depended upon by MAGNOLIA-4131 Activation doesn't work in integratio... Closed
relation
is related to MAGNOLIA-3904 Use public/private encryption to secu... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

http://hudson.magnolia-cms.com/job/magnolia-bundle_trunk/info.magnolia$magnolia-integration-tests/1742/consoleFull
[INFO] [talledLocalContainer] 2011-12-12 00:09:23,107 ERROR fo.magnolia.module.exchangesimple.SimpleSyndicator: Failed to activate content.
[INFO] [talledLocalContainer] info.magnolia.cms.exchange.ExchangeException: Not able to send the activation request http://localhost:8088/magnoliaTestPublic/.magnolia/activation: Server returned HTTP response code: 413 for URL: http://localhost:8088/magnoliaTestPublic/.magnolia/activation
[INFO] [talledLocalContainer] at info.magnolia.module.exchangesimple.BaseSyndicatorImpl.activate(BaseSyndicatorImpl.java:431)
[

to problem with Jetty buffer size http://jira.codehaus.org/browse/JETTY-336
Yes, we now send big header during the handshake op

The solution is to increase buffer size (as mentioned at the end of the issue) using
<Set name='headerBufferSize'>8192</Set>
in connector section of jetty.xml, however we don't use static jetty.xml file and http://cargo.codehaus.org/Jetty+6.x doesn't support dynamic setting of this attribute.
Tomcat doesn't suffer from the same issue.



 Comments   
Comment by Robert Šiška [ 25/May/12 ]

With Jetty6, the default header buffer size (the maximum length of the header the server can receive) was changed from 8KB to 4KB. (see http://jira.codehaus.org/browse/JETTY-336)

So far, the Jetty we use for integration tests used automatically generated jetty.xml config file. We needed to replace this file with our own config file with bigger header buffer size. I tried to specify the custom connector in Maven Jetty Plugin, but couldn't get the buffer size set (for some reason).

To solve this, I used <configfiles /> option of Maven Cargo Plugin, that can add/replace config files to container's dir. I used the Jetty's generated config file as a template.

Generated at Mon Feb 12 03:50:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.