Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-16945

[GSS](7.2.z) WFCORE-2516 - Changes to the logging subsystem are not persisted to the logging.properties in offline CLI

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Minor Minor
    • None
    • 7.2.1.GA
    • Logging
    • None
    • +
    • Workaround Exists
    • Hide

      unzip jboss
      rm standalone/configuration/logging.properties (and any other example configs you will not use)
      ./bin/jboss-cli.sh
      [disconnected /] embed-server
      /subsystem=logging/root-logger=ROOT:write-attribute(name=handlers, value=[CONSOLE])
      /subsystem=logging/periodic-rotating-file-handler=FILE:remove()
      exit
      ./bin/standalone.sh
      --------
      Or start standalone.sh and use jboss-cli.sh -c when configuring instead of the embedded server

      Show
      unzip jboss rm standalone/configuration/logging.properties (and any other example configs you will not use) ./bin/jboss-cli.sh [disconnected /] embed-server /subsystem=logging/root-logger=ROOT:write-attribute(name=handlers, value= [CONSOLE] ) /subsystem=logging/periodic-rotating-file-handler=FILE:remove() exit ./bin/standalone.sh -------- Or start standalone.sh and use jboss-cli.sh -c when configuring instead of the embedded server
    • Hide

      unzip jboss
      ./bin/jboss-cli.sh
      [disconnected /] embed-server
      /subsystem=logging/root-logger=ROOT:write-attribute(name=handlers, value=[CONSOLE])
      /subsystem=logging/periodic-rotating-file-handler=FILE:remove()
      exit
      ./bin/standalone.sh
      The server.log will be written until the logging subsystem takes over and then it will not write to server.log anymore.

      Show
      unzip jboss ./bin/jboss-cli.sh [disconnected /] embed-server /subsystem=logging/root-logger=ROOT:write-attribute(name=handlers, value= [CONSOLE] ) /subsystem=logging/periodic-rotating-file-handler=FILE:remove() exit ./bin/standalone.sh The server.log will be written until the logging subsystem takes over and then it will not write to server.log anymore.

      When using embed-server within offline CLI changes to the logging subsystem are not persisted to the logging.properties file.

      Do note that before we fix this we may want to consider a fix for WFCORE-157. The issue being that offline CLI is likely used to provision a server and that server may be configured in a different location. Since the jboss.server.log.dir or other relative-to property will be resolved and written as a fully-qualified path this could be an issue.

              jperkins-rhn James Perkins
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: