Uploaded image for project: 'Jetspeed 2'
  1. Jetspeed 2
  2. JS2-1099

Portlet application's error logs should be found in its own log file, not in jetspeed's log file.

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.1
    • Component/s: None
    • Labels:
      None

      Description

      Currently, if a portlet throws exception, then the exception is logged in the jetspeed log file instead of its own log file.
      This is because JetspeedContainerServlet cannot access the application's slf4j logger when available due to classloader boundary.
      This problem can be solved if a JetspeedLogger implements delegating to PA's logger if available by reflection.
      Also, it would not be a overhead to retrieve PA's logger because it can done only once when the servlet meets an exception.
      By the way, the other logs related to initialization/destroying of PA should be logged in jetspeed log file as it has been done.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            woon_san Woonsan Ko
            Reporter:
            woon_san Woonsan Ko
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development