Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 997638

Summary:	Using the add-handler operation on an async-handler doesn't write the handler property to the logging.properties file
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Kyle Lape <klape>
Component:	Logging	Assignee:	James Perkins <jperkins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikoleta Hlavickova <nziakova>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.1.0	CC:	pkremens
Target Milestone:	ER1
Target Release:	EAP 6.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-15 16:22:43 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 Kyle Lape 2013-08-15 20:38:19 UTC

Executing an add-handler operation does not write the handler.$NAME.handlers property to the logging.properties file.

Steps to reproduce:
Execute: /subsystem=logging/async-handler=rh_async:add(queue-length=1000)
Then: /subsystem=logging/async-handler=rh_async:add-handler(name=CONSOLE)
Check the logging.properties file and the handler.rh_async.handlers=CONSOLE property is not present.

Comment 1 JBoss JIRA Server 2013-09-20 21:36:22 UTC

James Perkins <jperkins> updated the status of jira WFLY-1713 to Resolved

Comment 2 JBoss JIRA Server 2013-09-20 21:36:22 UTC

James Perkins <jperkins> made a comment on jira WFLY-1713

I'm guessing this was fixed with the logmanager component upgrade. I can no longer duplicate the issue. Handlers now seem to be added correctly.

Comment 3 James Perkins 2013-09-20 21:42:39 UTC

This was fixed as part of the logmanager upgrade, https://bugzilla.redhat.com/show_bug.cgi?id=994700. The actual commit in the logmanager was https://github.com/jboss-logging/jboss-logmanager/commit/652500d04769983debd6d583fc600ba34cf58006.

Comment 4 JBoss JIRA Server 2013-09-20 21:43:23 UTC

James Perkins <jperkins> made a comment on jira WFLY-1713

I'm guessing this was fixed with the logmanager component upgrade. I can no longer duplicate the issue. Handlers now seem to be added correctly. The logmanager commit that fixed this was https://github.com/jboss-logging/jboss-logmanager/commit/652500d04769983debd6d583fc600ba34cf58006

Comment 5 Petr Kremensky 2013-09-23 06:50:55 UTC

Verified on 6.2.0.ER1