Issue Details (XML | Word | Printable)

Key: JERSEY-1470
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Unassigned
Reporter: Martin Matula
Votes: 0
Watchers: 0
Operations

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

Improved diagnostics

Created: 12/Oct/12 02:59 PM   Updated: 08/Aug/13 02:09 PM   Resolved: 08/Aug/13 02:09 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 2.2

Time Tracking:
Issue & Sub-Tasks
Issue Only
Original Estimate: 2 days, 6 hours
Original Estimate - 2 days, 6 hours
Remaining Estimate: 0 minutes
Remaining Estimate - 0 minutes
Time Spent: 1 week, 2 days, 21 hours
Time Spent - 1 week, 2 days, 21 hours

Issue Links:
Related
 

Tags:
Participants: arungupta and Martin Matula

  • Sub-Tasks:
  • All
  • Open

 Description  « Hide

Need to provide better error reporting - hints in the exception messages, info on the configuration (what resources and providers were loaded), exact version of Jersey used (perhaps in each error message), consider exposing MBean(s), provide guidelines on more descriptive error reporting (instead of logging the exception message, people should try to provide a more descriptive message relevant to the place in the code where the exception occurred (hints on what may have gone wrong) along with the original message). This feature needs to be split up into individual tasks that will be scheduled for milestones.



arungupta added a comment - 29/Oct/12 04:35 PM

The following GET method:

@GET
@Produces("application/xml")
public List<String> getList() { return list; }

reports only the following error:

[#|2012-10-26T13:52:47.839-0700|INFO|44.0|org.glassfish.jersey.server.ApplicationHandler|_ThreadID=83;_ThreadName=http-listener-1(2);_TimeMillis=1351284767839;_LevelValue=800;|[failed to localize] init.msg(Jersey: 2.0-m09 2012-10-15 12:52:42)|#]

And a detailed error message stating that Jersey could not find a suitable message body worker was missing.