Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-25819

Tools bundling log4j.properties can break logging.

    Details

      Description

      All tools should now be using the log4.jar from /common/lib to avoid classloader problems, however log4j uses the thread context classloader to load it's log4j.properties file, this means that if the first webapp is one that supplies a log4j.properties file it will use that one instead of the default one.

      This is because it's the first webapp that will be the first one to load the log4j.jar

      As an example delegated-access.war includes a log4j.properties on it's classpath. If it's forced to be the first webapp to load (renaming to 000delefated-access.war) then when logging is loaded the format is different.

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

                  Assignee:
                  buckett Matthew Buckett
                  Reporter:
                  buckett Matthew Buckett
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration