Description of problem: When the DV is installed with disabled audit/command logging, no artifacts required for logging to work are present in configuration files(org.teiid.COMMAND_LOG loggers, logging datasource,..). This causes problem when logging is turned on from web console. There is an exception on server complaining about the missing artifacts: 15:01:23,723 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 4) JBAS014612: Operation ("add") failed - address: ([ ("subsystem" => "logging"), ("logger" => "org.teiid.COMMAND_LOG") ]): java.lang.IllegalArgumentException: Handler "TEIID_COMMAND_LOG" is not found Version-Release number of selected component (if applicable): DV 6.2.0 ER3 Steps to Reproduce: 1.Install DV with default configuration (without admin/command logging enabled) 2.Start server 3.Configure audit/command logging via web console http://localhost:9990 4.Examine server logs for exception
Added 2 scripts: teiid-standalone-auditcommand-logging.cli teiid-domain-auditcommand-logging.cli These should be run by default. And if database logging is selected, do not run these scripts.
Tom, will require changes to the installer.
Van Halbert <vhalbert> updated the status of jira TEIID-3577 to Resolved
Added the following 2 scripts: teiid-standalone-auditcommand-logging.cli teiid-domain-auditcommand-logging.cli These should be run by default. But should not be run if the database logging is selected for configuration.
Yes, this will require installer changes.
The jobs to run these scripts have been added. I do not get an error when enabling audit logging from the web console. Thank you, Emmett Underhill
Steven Hawkins <shawkins> updated the status of jira TEIID-3577 to Closed