History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-3291
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Jeff Turner [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

500 errors should be logged

Created: 02/Mar/04 05:14 AM   Updated: 02/Mar/04 05:14 AM
Component/s: Administration
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Jeff Turner [Atlassian]
Since last comment: 228 weeks, 5 days ago
Labels:


 Description  « Hide
When JIRA breaks for some reason, and users see output of 500page.jsp, the JIRA admin typically wants to know about this. JIRA ought to log (to a special log4j category) all the info displayed on the screen.

A nice way to do with is create a bean containing all diagnostic info, whose toString() prints a nicely formatted log. The bean could be instantiated in the JSP with <webwork:bean> and rendered.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.