Occassional 400 responses from JWS 3 Tomcat

Solution Verified - Updated -

Issue

  • We see occassional 400 responses from JWS 3 Tomcat with the following exception:
java.lang.IllegalArgumentException: Request header is too large
    at org.apache.coyote.http11.InternalInputBuffer.fill(Unknown Source)
    at org.apache.coyote.http11.InternalInputBuffer.fill(Unknown Source)
    at org.apache.coyote.http11.InternalInputBuffer.parseHeader(Unknown Source)
    at org.apache.coyote.http11.InternalInputBuffer.parseHeaders(Unknown Source)
    at org.apache.coyote.http11.AbstractHttp11Processor.process(Unknown Source)
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(Unknown Source)
    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:745)
  • But header sizes are consistently the same so headers shouldn't actually be too large.

Environment

  • JBoss Enterprise Web Server (JWS) 3.0.2 and earlier
    • Tomcat 7
    • Tomcat 8

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content