Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-4582

Creating Async log handler with filter fails

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: 7.1.1.Final
    • Fix Version/s: None
    • Component/s: Logging
    • Labels:
    • Environment:

      Actually using JBEAP.ER5

    • Steps to Reproduce:
      Hide

      See description.

      Show
      See description.
    • Workaround Description:
      Hide

      See description.

      Show
      See description.

      Description

      When attempting to create a new Asynch Log Handler if you try to define a filter during initial argument the handler creation fails. The same behavior happens when attempting to update with a filter value.

      /subsystem=logging/async-handler=ASYNCH4/:add(queue-length=1024,overflow-action=BLOCK,filter=accept)

      { "address" => [ ("subsystem" => "logging"), ("async-handler" => "ASYNCH4") ], "operation" => "add", "queue-length" => 1024, "overflow-action" => "BLOCK", "filter" => "accept" }

      {
      "outcome" => "failed",
      "failure-description" => "JBAS014749: Operation handler failed: null",
      "rolled-back" => true,
      "response-headers" =>

      {"process-state" => "reload-required"}

      }

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jamezp James Perkins
                Reporter:
                spinder Simeon Pinder
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: