Bug 1170583

Summary:	JBoss Web Management Audit/Command Logging handler not found
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Jan Stastny <jstastny>
Component:	Configuration	Assignee:	Thomas Hauser <thauser>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	dlesage, thauser, vhalbert
Target Milestone:	ER5	Keywords:	QA-Closed
Target Release:	6.1.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	When changing configuration of Audit and Command logging via Web Management, an exception would sometimes be thrown.This issue has been resolved by changes to the CLI script. As a result, users can now change the configuration without encountering the exception.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-10 08:57:17 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 2014-12-04 11:36:55 UTC

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

Comment 1 Van Halbert 2014-12-04 20:21:37 UTC

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.

Comment 2 Van Halbert 2014-12-04 20:22:46 UTC

The updated script will be in the tepid-extensions project that is pulled.

Comment 3 JBoss JIRA Server 2014-12-05 13:51:22 UTC

Van Halbert <vhalbert> updated the status of jira TEIID-3241 to Resolved

Comment 4 Van Halbert 2014-12-05 13:53:21 UTC

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.

Comment 5 Van Halbert 2014-12-05 20:18:50 UTC

The script change will be automatically brought into the build.  So no other steps to take.

Comment 6 JBoss JIRA Server 2015-10-08 14:39:56 UTC

Steven Hawkins <shawkins> updated the status of jira TEIID-3241 to Closed