[teiid-issues] [JBoss JIRA] (TEIID-3241) Audit/Command Logging handler names do not match web console handler names

[Van Halbert (JIRA)]

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

Van Halbert resolved TEIID-3241.
--------------------------------
    Resolution: Done


> Audit/Command Logging handler names do not match web console handler names
> --------------------------------------------------------------------------
>
>                 Key: TEIID-3241
>                 URL: https://issues.jboss.org/browse/TEIID-3241
>             Project: Teiid
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 8.7.1
>            Reporter: Van Halbert
>            Assignee: Van Halbert
>             Fix For: 8.7.1
>
>
> When changing configuration of Audit and Command logging via Web Management, an exception is thrown in specific usecase, see the steps to reproduce below.
> Then even after server restart logging doesn't work. No changes noticed in standalone.xml during the configuration.
> Version-Release number of selected component (if applicable):
> DV 6.1.0 ER4
> How reproducible:
> Once after installation (further on the logging simply doesn't work)
> Steps to Reproduce:
> 1.Install DV with audit/command logging enabled
> 2.Start DV with bin/standalone.sh, check that logging works
> 3.Access http://localhost:9990/console/App.html#teiid-audit and unselect selected options
> 4.Apply
> 5.Select the previously deselected options again
> 6.Apply
> 7.See the server log in console
> 8.When there is server reload between unselecting and reselecting the options, then the exception is not raised, but the logging doesn't work afterwards.
> Actual results:
> java.lang.IllegalArgumentException: Handler "TEIID_AUDIT_LOG" is not found
> or
> java.lang.IllegalArgumentException: Handler "TEIID_COMMAND_LOG" is not found
> Expected results:
> Logging configured again



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)