[
https://issues.jboss.org/browse/SECURITY-603?page=com.atlassian.jira.plug...
]
Marcus Moyses resolved SECURITY-603.
------------------------------------
Resolution: Done
The memory leak was present in SimpleRoleGroup. It stores SimpleRoles in an ArrayList and
there was multiple entries for the same role there. Fixed by only adding new roles to the
ArrayList.
Long running thread leaks SimpleRole objects
--------------------------------------------
Key: SECURITY-603
URL:
https://issues.jboss.org/browse/SECURITY-603
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Identity
Affects Versions: PicketBox_v3_0_CR2
Environment: Tested on Mac OS X 10.6.7 with Java HotSpot(TM) 64-Bit Server VM
(build 19.1-b02-334, mixed mode) 1.6.0_24
Reporter: Marcus Moyses
Assignee: Marcus Moyses
Labels: jboss
Fix For: PicketBox_v4_0_ga
Attachments: simpleroletest.tar.gz
When invoking a long-running EJB method which makes a bunch of calls to some method in
another EJB, then JBoss leaks SimpleRole objects. The SimpleRole objects are not removed
by a manually triggered garbage collection.
The SimpleRole object leakage seems to go away if I remove the security domain in
jboss.xml. When running my jboss application during the night JBoss had 4GB of SimpleRole
objects.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira