disclose stack traces when an internal error (HTTP 500) happens

Aleksander Leber May 19, 2014

We have Atlassian JIRA (v6.1.5#6160-sha1:a61a0fc) How can we disclose stack traces in some errors. I have seen this solution https://confluence.atlassian.com/pages/viewpage.action?pageId=282174657but it does not work for us because there is no 500page.jsp file. How can we manage what is seen in stack traces?

We have also tried to change error500.soy, but than we get the standard tomcat 500 error.

How to solve this issue?

1 answer

0 votes
hoblerone May 28, 2015

Same problem here. Sometimes I see that ajax requests fail with a 500 status, but JIRA doesn't log the stacktrace in the log file, so it's impossible to find out what exactly failed and why.

I can't believe that actively NOT showing stacktraces is some kind of feature? Logging any exceptions after a 500 should be the default.

Suggest an answer

Log in or Sign up to answer