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.
    • Similar Issues:
      Show 10 results 

      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

          Activity

          Hide
          jamezp James Perkins added a comment -

          The syntax is incorrect. The value expected is an object. For an accept filter it would look something like filter={"accept"=>"true"}. So your full command should be:

          /subsystem=logging/async-handler=ASYNCH4:add(queue-length=1024,overflow-action=BLOCK,filter=\{"accept"=>"true"\})
          

          I will currently leave this open as the boolean value passed makes no real difference as to what the filter does. So passing false would be the same as passing true for an accept or deny filter.

          Show
          jamezp James Perkins added a comment - The syntax is incorrect. The value expected is an object. For an accept filter it would look something like filter={"accept"=>"true" }. So your full command should be: /subsystem=logging/async-handler=ASYNCH4:add(queue-length=1024,overflow-action=BLOCK,filter=\{"accept"=>"true"\}) I will currently leave this open as the boolean value passed makes no real difference as to what the filter does. So passing false would be the same as passing true for an accept or deny filter.
          Hide
          jamezp James Perkins added a comment -

          https://issues.jboss.org/browse/AS7-4791 should fix the issue with the odd command.

          Show
          jamezp James Perkins added a comment - https://issues.jboss.org/browse/AS7-4791 should fix the issue with the odd command.

            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:

                Development