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

[GSS](7.2.0) Inconsistency of formatters in console logging handler

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Minor
    • None
    • 7.1.0.DR9
    • Management
    • Low
    • +
    • Hide

      1. %WILDFLY_HOME/bin/standalone.sh

      2. %WILDFLY_HOME/bin/jboss-cli.sh --connect

      3. Print COLOR-PATTERN pattern-formatter

      [standalone@localhost:9990 /] /subsystem=logging/pattern-formatter=COLOR-PATTERN:read-attribute(name=pattern)
{
    "outcome" => "success",
    "result" => "%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"
}

      4. Print CONSOLE console-handler

      [standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:read-resource
{
    "outcome" => "success",
    "result" => {
        "autoflush" => true,
        "enabled" => true,
        "encoding" => undefined,
        "filter" => undefined,
        "filter-spec" => undefined,
        "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n",
        "level" => "INFO",
        "name" => "CONSOLE",
        "named-formatter" => "COLOR-PATTERN",
        "target" => "System.out"
    }
}
      Show
      1. %WILDFLY_HOME/bin/standalone.sh 2. %WILDFLY_HOME/bin/jboss-cli.sh --connect 3. Print COLOR-PATTERN pattern-formatter [standalone@localhost:9990 /] /subsystem=logging/pattern-formatter=COLOR-PATTERN:read-attribute(name=pattern) { "outcome" => "success" , "result" => "%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n" } 4. Print CONSOLE console-handler [standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:read-resource { "outcome" => "success" , "result" => { "autoflush" => true , "enabled" => true , "encoding" => undefined, "filter" => undefined, "filter-spec" => undefined, "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n" , "level" => "INFO" , "name" => "CONSOLE" , "named-formatter" => "COLOR-PATTERN" , "target" => " System .out" } }

    Description

      In logging subsystem the default CONSOLE console-handler is defined with COLOR-PATTERN named-formatter.
      And the COLOR-PATTERN named-formatter is defined with: 

      "%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"

      It is working as it is defined with colors in a console.

      standalone.xml
      ...
<subsystem xmlns="urn:jboss:domain:logging:3.0">
    <console-handler name="CONSOLE">
        <level name="INFO"/>
        <formatter>
            <named-formatter name="COLOR-PATTERN"/>
        </formatter>
    </console-handler>
...
    <formatter name="COLOR-PATTERN">
        <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>
    </formatter>
</subsystem>
...

      However there is a inconsistency in the CLI and EAP admin console views.

      In the CLI, CONSOLE formatter is: 

      "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"

      It is wrong and different with the working logging format in a console.

      JBoss CLI
      [standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:read-resource
{
    "outcome" => "success",
    "result" => {
        "autoflush" => true,
        "enabled" => true,
        "encoding" => undefined,
        "filter" => undefined,
        "filter-spec" => undefined,
        "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n",
        "level" => "INFO",
        "name" => "CONSOLE",
        "named-formatter" => "COLOR-PATTERN",
        "target" => "System.out"
    }
}

      It should be fixed like below:

      Expected result
      [standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:read-resource
{
    "outcome" => "success",
    "result" => {
        "autoflush" => true,
        "enabled" => true,
        "encoding" => undefined,
        "filter" => undefined,
        "filter-spec" => undefined,
        "formatter" => undefined,
        "level" => "INFO",
        "name" => "CONSOLE",
        "named-formatter" => "COLOR-PATTERN",
        "target" => "System.out"
    }
}

      Attachments

        Issue Links

          clones

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFCORE-2011 Inconsistency of formatter and named-formatter in console logging handler

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11825 [GSS](7.0.z) Inconsistency of formatter and named-formatter in console logging handler

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rpelisse@redhat.com Romain Pelisse
              rhn-support-jwon Ted Won
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: