[jboss-jira] [JBoss JIRA] (WFLY-1952) Remove file-handler in Audit Log causes problems

[Ondrej Lukas (JIRA)]

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

Ondrej Lukas updated WFLY-1952:
-------------------------------

    Description: 
I'll use these six CLI commands (running standalone mode of WildFly):

        1) /core-service=management/access=audit/file-handler=audit-test-file-handler:add(formatter=json-formatter,path=/tmp/audit-test.log)
                add new file handler
        2) /core-service=management/access=audit/logger=audit-log/handler=audit-test-file-handler:add()
                register file handler to logger handlers
        3) /core-service=management/access=audit/logger=audit-log:write-attribute(name=enabled,value=true)
                enable audit log
        4) /core-service=management/access=audit/logger=audit-log:write-attribute(name=enabled,value=false)
                disable audit log
        5) /core-service=management/access=audit/logger=audit-log/handler=audit-test-file-handler:remove()
                unregister file handler from logger handlers
        6) /core-service=management/access=audit/file-handler=audit-test-file-handler:remove()
                remove file handler

The first weird behavior is running commands sequence 1, 2, 5 - it fails with:
{
    "outcome" => "failed",
    "failure-description" => "JBAS014749: Operation handler failed: JBAS013465: Attempt was made to both remove and add a handler reference from a composite operation",
    "rolled-back" => true
}

The next interesting behavior is running commands sequence 1, 2, 3, 4, 5, 6 - everything has "outcome" => "success" (and audit-test-file-handler isn't visit in standalone.xml) but if you repeat sequence 1, 2, 3, 4, 5, 6 then commands 1, 2, 5, 6 have "outcome" => "failed". However if you repeat sequence 1, 2, 3, 4, 5, 6 everything is ok again. And this behavior is repeated again and again. However, if I run sequence, stop and start server and run it again it works fine, but if I run sequence, call reload operation in CLI and run sequence again it fails.
If I do a little change in sequence to 1, 2, 3, 5, 6, 4 it succeeds in every cycle.

  was:
I'll use these six CLI commands (running standalone mode of WildFly):

        1) /core-service=audit-log/file-handler=audit-test-file-handler:add(formatter=json-formatter,path=/tmp/audit-test.log)
                - add new file handler
        2) /core-service=audit-log/logger=audit-log/handler=audit-test-file-handler:add()
                - register file handler to logger handlers
        3) /core-service=audit-log/logger=audit-log:write-attribute(name=enabled,value=true)
                - enable audit log
        4) /core-service=audit-log/logger=audit-log:write-attribute(name=enabled,value=false)
                - disable audit log
        5) /core-service=audit-log/logger=audit-log/handler=audit-test-file-handler:remove()
                - unregister file handler from logger handlers
        6) /core-service=audit-log/file-handler=audit-test-file-handler:remove()
                - remove file handler

The first weird behavior is running commands sequence 1, 2, 5 - it fails with:
{
    "outcome" => "failed",
    "failure-description" => "JBAS014749: Operation handler failed: JBAS013465: Attempt was made to both remove and add a handler reference from a composite operation",
    "rolled-back" => true
}

The next interesting behavior is running commands sequence 1, 2, 3, 4, 5, 6 - everything has "outcome" => "success" (and audit-test-file-handler isn't visit in standalone.xml) but if you repeat sequence 1, 2, 3, 4, 5, 6 then commands 1, 2, 5, 6 have "outcome" => "failed". However if you repeat sequence 1, 2, 3, 4, 5, 6 everything is ok again. And this behavior is repeated again and again. However, if I run sequence, stop and start server and run it again it works fine, but if I run sequence, call reload operation in CLI and run sequence again it fails.
If I do a little change in sequence to 1, 2, 3, 5, 6, 4 it succeeds in every cycle.


    
> Remove file-handler in Audit Log causes problems
> ------------------------------------------------
>
>                 Key: WFLY-1952
>                 URL: https://issues.jboss.org/browse/WFLY-1952
>             Project: WildFly
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 8.0.0.Alpha4
>            Reporter: Ondrej Lukas
>            Assignee: Kabir Khan
>
> I'll use these six CLI commands (running standalone mode of WildFly):
>         1) /core-service=management/access=audit/file-handler=audit-test-file-handler:add(formatter=json-formatter,path=/tmp/audit-test.log)
>                 add new file handler
>         2) /core-service=management/access=audit/logger=audit-log/handler=audit-test-file-handler:add()
>                 register file handler to logger handlers
>         3) /core-service=management/access=audit/logger=audit-log:write-attribute(name=enabled,value=true)
>                 enable audit log
>         4) /core-service=management/access=audit/logger=audit-log:write-attribute(name=enabled,value=false)
>                 disable audit log
>         5) /core-service=management/access=audit/logger=audit-log/handler=audit-test-file-handler:remove()
>                 unregister file handler from logger handlers
>         6) /core-service=management/access=audit/file-handler=audit-test-file-handler:remove()
>                 remove file handler
> The first weird behavior is running commands sequence 1, 2, 5 - it fails with:
> {
>     "outcome" => "failed",
>     "failure-description" => "JBAS014749: Operation handler failed: JBAS013465: Attempt was made to both remove and add a handler reference from a composite operation",
>     "rolled-back" => true
> }
> The next interesting behavior is running commands sequence 1, 2, 3, 4, 5, 6 - everything has "outcome" => "success" (and audit-test-file-handler isn't visit in standalone.xml) but if you repeat sequence 1, 2, 3, 4, 5, 6 then commands 1, 2, 5, 6 have "outcome" => "failed". However if you repeat sequence 1, 2, 3, 4, 5, 6 everything is ok again. And this behavior is repeated again and again. However, if I run sequence, stop and start server and run it again it works fine, but if I run sequence, call reload operation in CLI and run sequence again it fails.
> If I do a little change in sequence to 1, 2, 3, 5, 6, 4 it succeeds in every cycle.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira