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

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

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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,316 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot