#1001 Handling unchecked exception
Closed: migrated 3 years ago by dmoluguw. Opened 9 years ago by edewata.

When a REST method throws an unchecked exception (e.g. RuntimeException, Error, or Throwable), by default the exception will be passed to the client as Internal Server Error without any details. The server logs will not have any info either unless the method explicitly catches all exceptions and logs the stack trace. This makes troubleshooting harder.

A possible solution is to use RESTEasy's ExceptionMapper to catch all exceptions then log the stack trace and generate a PKIException that includes the original exception's message.

Proposed milestone: 10.2 backlog


Per PKI/389 Meeting of 05/19/2014, moving to Milestone 10.2 Backlog.

Proposed Milestone: 10.2.2 (per CS Meeting of 09/17/2014)

Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog

Per 10.2.3 TRIAGE meeting of 02/26/2015: 10.3

NOTE: Moved from 10.2 Backlog since it was not a documentation/man page issue.

Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1567

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata