The jira service will display a blank page after logging in every day recently, and the configuration has not been changed recently, and the log content is not very helpful. It will return to normal after each restart. Ask for help! ! ! Operating system: CentOS release 6.5 jira version: v7.3.6 At 9:32 on March 24, there is a prompt for a wrong password, and a blank page will be displayed after the password is correct. The following picture shows the login screenshot:
atlassian-jira.log log output:
2021-03-24 05:09:32,014 http-nio-8090-exec-3 DEBUG anonymous 309x212965x2-220.127.116.11 / [c.a.j.web.filters.ThreadLocalQueryProfiler] PROFILED: 0 keys (0 unique) took 0ms/23ms: 0.0% 2021-03-24 05:09:32,147 http-nio-8090-exec-7 DEBUG anonymous 309x212966x2-18.104.22.168 / [c.a.util.profiling.UtilTimerStack] [22ms]-/ [17ms]-MyJiraHome.execute() [14ms]-Dashboard.execute()
2021-03-24 05:09:32,147 http-nio-8090-exec-7 DEBUG anonymous 309x212966x2-22.214.171.124 / [c.a.j.web.filters.ThreadLocalQueryProfiler] PROFILED: 0 keys (0 unique) took 0ms/22ms: 0.0%
catalina.out log output(The following log has always existed before and didn't care about it) :
24-Mar-2021 05:09:28.057 INFO [http-nio-8090-exec-5] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:462) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:667) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:802) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1410) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745)
24-Mar-2021 09:32:51.611 WARNING [http-nio-8090-exec-20] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://jira. hapjs.org/rest/gadget/1.0/login, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
Hi @raoweiheng , I think it is some problem of your browser. I found this thread (https://stackoverflow.com/questions/29894154/chrome-neterr-incomplete-chunked-encoding-error). Could you check your antivirus software?
The server is a linux system. When the problem occurs, I try to access multiple computers and different browsers, but the problem still exists. The "net::ERR_INCOMPLETE_CHUNKED_ENCODING 200" in the above figure is an error reported after jira is closed, otherwise the resource is always loaded. Screen
can you rule out any App is causing this? Be sure to spot any outdated/incompatible Apps.
Probably clearing the plugin cache (according to: https://jira.atlassian.com/browse/JRASERVER-27314) could help should it turn out an App is involved.
If you feel an App is contributing to the blank page putting Jira into safe mode (through UPM) could be an idea - just make sure you test this outside office hours to not disturb users.
Also your Jira version seems a bit dated. Probably an upgrade to a recent version could contribute and have a positive effect.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events