Issue Details (XML | Word | Printable)

Key: JRA-15049
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Nick Menere [Atlassian]
Votes: 0
Watchers: 0
Operations

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

Add better debugging information to portlet rendering

Created: 03/Jun/08 09:23 PM   Updated: 21/Aug/08 09:54 PM
Component/s: Portlets
Affects Version/s: None
Fix Version/s: 3.13

Time Tracking:
Original Estimate: 3 hours
Original Estimate - 3 hours
Remaining Estimate: 0 minutes
Time Spent - 3 hours
Time Spent: 3 hours
Time Spent - 3 hours

Participants: Nick Menere [Atlassian]
Since last comment: 7 weeks, 3 days ago
Resolution Date: 21/Aug/08 09:54 PM
Labels:


 Description  « Hide
It is quite easy to get portlets into a bad shape.
E.g. Deleting customfields for 2dStats Portlet

We should put a nice big high level try/catch block in - com.atlassian.jira.web.portlet.bean.PortletRenderer.renderPortlet or com.atlassian.jira.portal.PortletImpl.getViewHtml that at least logs:
An error was thrown while try to render portlet: 1234
This would make debugging of support cases much, much easier.

We can either rethrow the error or print a nice message:
We were unable to render this portlet due to an internal error. Please contact your JIRA Administrator



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Nick Menere [Atlassian] added a comment - 21/Aug/08 09:54 PM
This has gone in.