Description of problem: 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
The fix is to correct the teiid-add-database-logger.cli script. Assigning to Tom so that the update script is picked up when the cli-scripts are packaged.
The updated script will be in the tepid-extensions project that is pulled.
Van Halbert <vhalbert> updated the status of jira TEIID-3241 to Resolved
The change has been committed to the product branch, but need to check with Tom to ensure this cli script is picked up in the build.
The script change will be automatically brought into the build. So no other steps to take.
Steven Hawkins <shawkins> updated the status of jira TEIID-3241 to Closed