Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Issue Links

          Activity

          Martin Matula created issue -
          Martin Matula made changes -
          Field Original Value New Value
          Fix Version/s 2.0-m10 [ 16087 ]
          Fix Version/s 2.0-backlog [ 15363 ]
          Jakub Podlesak made changes -
          Link This issue is related to JERSEY-1430 [ JERSEY-1430 ]
          Hide
          arungupta added a comment -

          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.

          Show
          arungupta added a comment - 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.
          Pavel Bucek made changes -
          Fix Version/s 2.0-m11 [ 16171 ]
          Fix Version/s 2.0-m10 [ 16087 ]
          Pavel Bucek made changes -
          Fix Version/s 2.0-m12 [ 16248 ]
          Fix Version/s 2.0-m11 [ 16171 ]
          Pavel Bucek made changes -
          Fix Version/s 2.0-backlog [ 15363 ]
          Fix Version/s 2.0-m12 [ 16248 ]
          Marek Potociar made changes -
          Fix Version/s 2.0 [ 15271 ]
          Marek Potociar made changes -
          Priority Blocker [ 1 ] Critical [ 2 ]
          Marek Potociar made changes -
          Fix Version/s 2.0-rc2 [ 16380 ]
          Fix Version/s 2.0 [ 15271 ]
          Fix Version/s 2.x-backlog [ 15363 ]
          Pavel Bucek made changes -
          Fix Version/s 2.0-rc2 [ 16380 ]
          Marek Potociar made changes -
          Fix Version/s 2.1 [ 16421 ]
          Fix Version/s 2.0 [ 15271 ]
          Miroslav Fuksa made changes -
          Fix Version/s 2.2 [ 16505 ]
          Fix Version/s 2.1 [ 16421 ]
          Libor Kramolis made changes -
          Fix Version/s 2.3 [ 16610 ]
          Fix Version/s 2.2 [ 16505 ]
          Marek Potociar made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Fix Version/s 2.2 [ 16505 ]
          Fix Version/s 2.3 [ 16610 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Martin Matula
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days, 6 hours Original Estimate - 2 days, 6 hours
                2d 6h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 week, 2 days, 21 hours
                1w 2d 21h