glassfish
  1. glassfish
  2. GLASSFISH-18205

Changing a log level via Admin Console breaks logging

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.1.2_b17
    • Component/s: admin_gui
    • Labels:
      None
    • Environment:

      Windows XP

      Description

      I have somehow broken logging in my Glassfish 3.1.1 deployment.

      All I did was attempt to bump up the level of one of the logs, via the "Logger Settings" view under Configurations -> server-config. I went to the "Log Levels" tab, found "javax.enterprise.system.core.security" and bumped it up from INFO to FINEST, then clicked Save.

      From that point on, the last message in the log is "Updated log levels for loggers." Nothing else ever gets written to the logs anymore! I can stop, restart the server, but the log never changes. I decided to go UNDO that change to see if it would fix it, but it did not. I think there must be some kind of side effect that breaks logging when you try to set the levels via this "Logger Settings" interface.

      I reinstalled Glassfish from scratch, and was able to reproduce it again. Just setting that one value to FINEST breaks logging.

      Is this a known issue, and if so, are there any workarounds?

        Issue Links

          Activity

          Hide
          Anissa Lam added a comment -

          Yes, this is a known issue in 3.1.1.
          The cause is due to GLASSFISH-17037 which is release noted.
          This is a duplicate of GLASSFISH-17161

          The workaround is to run a CLI command after adjusting/changing the log levels in console.

          %asadmin set-log-levels com.sun.enterprise.server.logging.GFFileHandler=ALL

          Specify the --target option for a server instance if it is not the domain administration server (DAS).

          Show
          Anissa Lam added a comment - Yes, this is a known issue in 3.1.1. The cause is due to GLASSFISH-17037 which is release noted. This is a duplicate of GLASSFISH-17161 The workaround is to run a CLI command after adjusting/changing the log levels in console. %asadmin set-log-levels com.sun.enterprise.server.logging.GFFileHandler=ALL Specify the --target option for a server instance if it is not the domain administration server (DAS).

            People

            • Assignee:
              Anissa Lam
              Reporter:
              kevinpauli
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: