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

Not possible to edit named formatter of most logging handlers

XMLWordPrintable

    • Regression
    • Hide
      1. start EAP with e.g. standalone-full-ha.xml configuration
      2. using CLI create console handler, e.g. 
        /subsystem=logging/console-handler=test-console-handler:add
      3. using web console navigate Configuration: Subsystems > Subsystem: Logging > Handler > Console
      4. Select test-console-handler
      5. Edit
      6. In the Formatter field delete the default value to deal with the new alternatives validation
      7. In the Named formatter field fill PATTERN
      8. Save
      Show
      start EAP with e.g. standalone-full-ha.xml configuration using CLI create console handler, e.g. /subsystem=logging/console-handler=test-console-handler:add using web console navigate Configuration: Subsystems > Subsystem: Logging > Handler > Console Select test-console-handler Edit In the Formatter field delete the default value to deal with the new alternatives validation In the Named formatter field fill PATTERN Save

      Following error is caused by the need to erase default value from Formatter field to comply with the new alternatives validation. This doesn't seem to be possible in the composite operation called by the console. As a consequence the named formatter field is not editable in EAP 7.1.0.DR19 web console in contrary to the EAP 7.0.0 web console.
      Handlers affected:

      • console-handler
      • file-handler
      • periodic-rotating-file-handler
      • periodic-size-rotating-file-handler
      • size-rotating-file-handler
      Failed to modify resource [ ("subsystem" => "logging"), ("console-handler" => "test-console-handler") ]

Unexpected HTTP response: 500

Request
{
    "operation" => "composite",
    "address" => [],
    "steps" => [
        {
            "address" => [
                ("subsystem" => "logging"),
                ("console-handler" => "test-console-handler")
            ],
            "operation" => "undefine-attribute",
            "name" => "formatter"
        },
        {
            "address" => [
                ("subsystem" => "logging"),
                ("console-handler" => "test-console-handler")
            ],
            "operation" => "write-attribute",
            "name" => "named-formatter",
            "value" => "PATTERN"
        }
    ]
}

Response

Internal Server Error
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: Formatter \"test-console-handler\" is not found",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "rolled-back" => true
        }
    },
    "failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: Formatter \"test-console-handler\" is not found"}},
    "rolled-back" => true
}

              thofman Tomas Hofman
              pjelinek@redhat.com Pavel Jelinek
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: