HTTP Status 400 - Bad Request error observed

Steve Andrew_nzyjp5

Hi All,

I am getting HTTP Status 400 - Bad Request error whenever I am clicking on Test Cases allocated to any team member in my Project.

I have created a filter wherein the Test Cases are over 300 and have been allocated to 15 team members but when clicked on any Team member's total test cases allocated then the error occurs again and again. Tried clearing cache, restarting the browser, clearing history and cookies, opened an Incognito window and logged into JIRA Cloud but still the same issue persists.

Issue observed is as follows:

Type Exception Report

Message Request header is too large

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Exception

java.lang.IllegalArgumentException: Request header is too large
	org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:766)
	org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:921)
	org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:594)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:283)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1590)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Unknown Source)

Note The full stack trace of the root cause is available in the server logs.

Unable to understand how to resolve the issue.

Kindly help in resolving the issue asap.

Thanks & Regards,

Steve Andrew

Earl McCutcheon

Hello @Steve Andrew ,

Thanks for reaching out, and I have a question about some of the information you noted.  You mentioned having access to the server logs for the full stack trace but this thread is listed with a Jira Cloud tag where on the cloud platform you would not have access to logging, so I just wanted to clarify what you meant by this and the platform you are on as a first step, so are you on the Jira Cloud platform or are you on a Data Center Deployment.

Next what tool are you using for test case management, as the behavior is most likely tied to the add-on app that you are using for this and you may need to reach out to the application vendor for additional support.

Next looking into a solution the following KB article gives more details about this error, and some troubleshooting steps:

• Jira users receiving the error 400 Bad Request: Message Request header is too large

Noting on the cloud platform you would only be able to apply the Client side troubleshooting steps:

Solution

1) Client-side:

1. Clear Browser Cache.
2. Clear Browser Cookies.
3. File Upload Exceeds Server Limit.
4. Deactivate Browser Extensions.

Check this out and let me know what you find

Regards,
Earl