[jboss-jira] [JBoss JIRA] (AS7-4582) Creating Async log handler with filter fails

[James Perkins (JIRA)]

     [ https://issues.jboss.org/browse/AS7-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins resolved AS7-4582.
--------------------------------

    Resolution: Rejected


https://issues.jboss.org/browse/AS7-4791 should fix the issue with the odd command.
                
> Creating Async log handler with filter fails
> --------------------------------------------
>
>                 Key: AS7-4582
>                 URL: https://issues.jboss.org/browse/AS7-4582
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 7.1.1.Final
>         Environment: Actually using JBEAP.ER5
>            Reporter: Simeon Pinder
>            Assignee: James Perkins
>              Labels: rhq
>
> 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"}
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira