Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-8773

Log configuration errors are hard to debug

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • No Release
    • None
    • None
    • None
    • Workaround Exists
    • Hide

      In the event that logging just "ends", you can disable the bootstrap handler removal service in the deployers/jboss-logging.deployer/META-INF/logmanager-jboss-beans.xml file (it's the service called "JBossLogService"). You'll also have to remove the dependency on that service created by the "Logging:CONTEXT:system" service.

      Show
      In the event that logging just "ends", you can disable the bootstrap handler removal service in the deployers/jboss-logging.deployer/META-INF/logmanager-jboss-beans.xml file (it's the service called "JBossLogService"). You'll also have to remove the dependency on that service created by the "Logging:CONTEXT:system" service.

      Because of the way the log services are coordinated, some log configuration problems and runtime errors do not occur until after the bootstrap log handlers have already been removed. It would be better to not remove these handlers until the new ones are known to be good. Maybe by using replaceHandlers() in the logger service.

              Unassigned Unassigned
              dlloyd@redhat.com David Lloyd
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated: