HTTP Status 400 – Bad Request error in activity stream

simon.schneider

Hi everyone,

 

I am facing problems using the JIRA activity streams for a few months now. Problem is that sometimes (unregulary, every few days) the activity stream in my dashboard shows following error:

HTTP Status 400 – Bad Request

---

Type Exception Report

Message Request header is too large

Beschreibung 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(ThreadPoolExecutor.java:1149)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Thread.java:748)

Hinweis Der komplette Stacktrace der Ursache ist in den Server logs zu finden


And there is no result shown ofcourse. Has anyone an idea of what is happening there? 
Most of the time however, the stream works fine. Configuration was not changed recently.

Andy Heinzer

Hi Simon,

Sorry to hear about this problem.  I understand you are using Jira Cloud and sometimes seeing this 400 Bad request error when trying to view the activity stream. 

I researched this particular error, however I only found one other support case with this error in the past year.  In that case, it was found that this was specific to a single user's browser session.  In the testing done, both using a different browser, as well as the incognito (or private) browsing mode could not reproduce this error.

So I would recommend starting there to better understand this problem.  If there are other users that also have this same problem, that too would be good to find out if possible.  If using incognito mode works, then it might be a good idea to clear out the cookies and browser cache as a short term solution here.

If you do that, and find that this error still occurs later on, then I would be more interested for you generate a HAR file.  This file will contain more information about what is happening in your browser.  However this is not a file you would want to share on our public forum here in Community as it will contain your cookie.  Instead, I would then recommend you reach out to your Jira Cloud site-admin and ask them to open a support request on your behalf at https://support.atlassian.com/contact/ Those site-admins of non-free Cloud subscriptions can get support from Atlassian, and you can upload that har file privately there for our review.  Perhaps there is something else we might want to more closely investigate on your Cloud site as well that might be a factor here.

I hope this helps.

Andy