Bug 1324572

Summary:	[GSS](6.4.z) LogContexts are not removed for ear subdeployments
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Aaron Ogburn <aogburn>
Component:	Logging	Assignee:	Aaron Ogburn <aogburn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikoleta Hlavickova <nziakova>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.4.7	CC:	bmaxwell, brian.stansberry, jbilek, jperkins, jtruhlar, msochure, rnetuka
Target Milestone:	CR1
Target Release:	EAP 6.4.9
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 12:56:10 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:
Bug Depends On:
Bug Blocks:	1324262, 1324980

Description Aaron Ogburn 2016-04-06 16:29:57 UTC

Description of problem:

If an ear does not have its own LogContext created, but a subdeployment in it does, the subdeployment never has its LogContext cleaned up upon undeploy, leading to PermGen leaks.


How reproducible:

Very

Steps to Reproduce:
1. Set trace logging for 'org.jboss.as.logging' to easily see log context adds and removals.
2. Deploy attached ear
3. undeploy ear
4. Note the log context is not removed

Actual results:

Log context is not removed for subdeployments

Expected results:

Log context is removed for subdeployments

Additional info:

Comment 4 Jiří Bílek 2016-06-21 14:04:18 UTC

Verified with 6.4.9.CP.CR1

Comment 5 JBoss JIRA Server 2016-08-23 11:38:48 UTC

Jiri Pallich <jpallich> updated the status of jira JBEAP-4101 to Closed

Comment 6 Petr Penicka 2017-01-17 12:56:10 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.