Bug 1240673

Summary: Audit/Command logging can't be turned on in web console
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Jan Stastny <jstastny>
Component: Configuration, InstallerAssignee: Thomas Hauser <thauser>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Stastny <jstastny>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: aszczucz, atangrin, dlesage, eunderhi, thauser, vhalbert
Target Milestone: CR1Keywords: QA-Closed
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 08:54:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Stastny 2015-07-07 13:25:15 UTC
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

Comment 1 Van Halbert 2015-07-15 19:58:07 UTC
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.

Comment 2 Van Halbert 2015-07-15 19:58:32 UTC
Tom,

will require changes to the installer.

Comment 3 JBoss JIRA Server 2015-07-16 12:46:22 UTC
Van Halbert <vhalbert> updated the status of jira TEIID-3577 to Resolved

Comment 4 Van Halbert 2015-07-16 12:47:48 UTC
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.

Comment 5 Thomas Hauser 2015-07-27 14:39:45 UTC
Yes, this will require installer changes.

Comment 6 Emmett Underhill 2015-08-26 17:32:59 UTC
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

Comment 7 JBoss JIRA Server 2015-10-11 19:18:36 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-3577 to Closed