Logback configuration runtime reloading does not work as expected

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • VOMS Admin server v. 3.6.0
    • Affects Version/s: VOMS Admin server v. 3.5.1
    • Component/s: admin-server
    • Security Level: Public (Visbile by non-authn users.)
    • None

      Logback implements configuration scanning, so that loggers are reconfigured as a result of a change in the vo configuration file.
      This mechanism works fine for the VOMS Admin container log configuration, but breaks for VO configuration. When the logging configuration is reloaded, the vo.name parameter is lost and the log is sent to a file named:

      voms-admin-VOMS.VO.NAME-IS-UNDEFINED.log

            Assignee:
            Unassigned
            Reporter:
            Andrea Ceccanti
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: