504 Gateway Time-out when logging into to JIRA

[deirdrerodgers]

Hello

Today we are unable to log in to JIRA version (v8.3.2)

After clicking to log-in it keeps loading and then we eventually get a 504 gateway time out.

Logs are showing below

2019-10-16T07:54:47.201+0000: 55347.827: [GC (Allocation Failure) [PSYoungGen: 665268K->19166K(664064K)] 1750663K->1105164K(1762304K), 0.0510860 secs] [Times: user=0.13 sys=0.00, real=0.05 secs]

I saw online this is associated with memory issues but when I check memory on my server all looks good

[root@ip-10-92-60-99 bin]# free -m

             total       used       free     shared    buffers     cached

Mem:         15468       9859       5608          0        421       6813

-/+ buffers/cache:       2624      12843

Swap:            0          0          0

[Shankar Asam {Appfire}]

Hi,

504 gateway error typically comes from a proxy or a web server which is front ended to your JIRA server. If you are using apache or nginx proxy, pls see if it's working properly and serving the requests. You can also check the atlassian-jira.log file for any errors coming from JIRA side. The above logs didn't help much

-Shankar

[deirdrerodgers]

Hi @Shankar Asam {Appfire} Shankar,

Cant see anything in the atlassian-jira.log file in terms of errors unfortunately

the tomcat log shows this

16-Oct-2019 10:17:21.398 WARNING [http-nio-8080-exec-20] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira.pgi-tools.com/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.

[deirdrerodgers]

@Shankar Asam {Appfire} 

Hi Shankar,

I am seeing the below error in the tomcat logs

16-Oct-2019 10:33:20.155 WARNING [http-nio-8080-exec-14] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira.bla-tools.com/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.
16-Oct-2019 10:33:29.023 WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [http-nio-8080-exec-14] (id=[33]) was previously reported to be stuck but has completed. It was active for approximately [135,345] milliseconds.

[Shankar Asam {Appfire}]

{panel}

[ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [http-nio-8080-exec-14] (id=[33]) was previously reported to be stuck but has completed. It was active for approximately [135,345] milliseconds.

{panel}

The above one is a warning and can be ignored as some http thread was previously reported to be stuck but has completed. The resource has become free now (as per the message). Please check to see if there are any background jobs (scheduled jobs) were running during that time. Thread dumps over time are still the best way to diagnose long running threads. 

-Shankar