Ticket #474 (closed Defect: fixed)

Opened 7 years ago

Last modified 7 years ago

Not all exceptions appear in the log file

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.2
Component: DeepaMehta Standard Distribution Version: 4.1
Keywords: Cc: dgf, Malte
Complexity: 3 Area:
Module:

Description (last modified by jri) (diff)

When file logging is activated some exceptions are not logged into the log file but on the console.

In particular this applies to exceptions thrown from a Servlet filter.
It seems the servlet container (Jetty) does not log through the Java logging API. Fact is the java.util.logging.config.file system property as set by DM is not respected within a Servlet filter class.

Thank you very much, Malte, for reporting!

Change History

comment:1 Changed 7 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 7 years ago by jri

  • Description modified (diff)

comment:3 Changed 7 years ago by Jörg Richter

Access Control: fix exception logging (#474).

When file logging is activated exceptions thrown from the Access Control's request filter are logged into the log file.

See ticket 474.

comment:4 Changed 7 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed

Access Control: fix exception log (#474, #484).

Exceptions thrown by the Access Control's request filter are not logged twice on the console.
If file logging is activated all excpetions are logged properly.
Generally, since the Servlet Filter is dropped (see #448) exception handling is more straight forward.

Exceptions thrown by resource methods and event listeners are logged more clearly.

Close #474.
Close #484.

Changeset: 2b587af7e68b50d8ca45697fb3a6a129d92585fb

Note: See TracTickets for help on using tickets.