Bug 1131633

Summary:	OutOfMemoryError when CI is ran with tracing
Product:	[JBoss] JBoss Data Grid 6	Reporter:	William Burns <wburns>
Component:	Infinispan	Assignee:	Tristan Tarrant <ttarrant>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Gencur <mgencur>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3.1, 6.4.0	CC:	jdg-bugs, vjuranek
Target Milestone:	ER2
Target Release:	6.3.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1139642 (view as bug list)		Environment:
Last Closed:	2015-01-26 14:05:58 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:	1139642

Description William Burns 2014-08-19 17:34:17 UTC

Description of problem:

Log4j1.2 causes a memory leak when using the NDC which is set per thread.  This should be a rather trivial leak unless a large amount of threads are destroyed and created which can happen for production over a long period of time possibly.

The reason CI saw it was because these threads were shared in the same process as multiple servers were started and stopped so they continually added up.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 William Burns 2014-08-19 17:55:37 UTC

Note the leak only occurs when tracing was enabled, so it shouldn't happen normally.

Comment 3 Vojtech Juranek 2014-09-05 14:32:23 UTC

For the record: done in https://github.com/infinispan/jdg/commit/cfd928eb09c1bcc9a039c99ff0bac6d3b68839e6