[#JOSSO-221] BaseRoleImpl objects increase in memory - Atricore

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: JOSSO 1.8, JOSSO 1.8.1, JOSSO 1.8.2
Fix Version/s: JOSSO 1.8.2
Component/s: None

Description:

Hide
This was originally posted on the forum the text is,

We are running JBOSS 4.2.2 with JOSSO 1.8, and are having memory issues with JBOSS (Arent we all!)

So to look at what is going on we have a profiling tool (jprofiler) to see where memory and resources are being used on the server. One candidate that seems to be holding memory is JOSSO.

The "org.josso.gateway.identity.service.BaseRoleImpl" class seems to increase in instances in memory (by 19 each login/out) every time someone logs in, even if they log out again the memory is not cleared.

The "org.josso.gateway._1.1.protocol.SSORoleType" class also seems to grow in instances in memory (by 17 each login/out) after each log in/out. Again, these are never cleared.

I have been testing things out, and have changed the session and assertion stores to be be database stores in place of the memory stores I had, but that doesn't seem to make any difference.

The original post can be seen at : https://sourceforge.net/projects/josso/forums/forum/399715/topic/3700885

This memory leeks needs to be looked at and the leak identified and rectified

Show
This was originally posted on the forum the text is, We are running JBOSS 4.2.2 with JOSSO 1.8, and are having memory issues with JBOSS (Arent we all!) So to look at what is going on we have a profiling tool (jprofiler) to see where memory and resources are being used on the server. One candidate that seems to be holding memory is JOSSO. The "org.josso.gateway.identity.service.BaseRoleImpl" class seems to increase in instances in memory (by 19 each login/out) every time someone logs in, even if they log out again the memory is not cleared. The "org.josso.gateway._1.1.protocol.SSORoleType" class also seems to grow in instances in memory (by 17 each login/out) after each log in/out. Again, these are never cleared. I have been testing things out, and have changed the session and assertion stores to be be database stores in place of the memory stores I had, but that doesn't seem to make any difference. The original post can be seen at : https://sourceforge.net/projects/josso/forums/forum/399715/topic/3700885 This memory leeks needs to be looked at and the leak identified and rectified

Environment:

RHEL 4, Sun Java 1.5, Jboss 4.2.2, also tried on Mac OSX, Apple Java 1.5, Jboss 4.2.2

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Andrew Crowe added a comment - 11/May/10 10:39 AM

Since raising this issue in the forum I have also tested with JOSSO 1.8.2, and that also has the same issue.

Show

Andrew Crowe added a comment - 11/May/10 10:39 AM Since raising this issue in the forum I have also tested with JOSSO 1.8.2, and that also has the same issue.

Hide

Permalink

Sebastian Gonzalez Oyuela added a comment - 27/Jul/10 7:59 AM

Keep in mind that JBoss keeps a cache of JAAS Login module instances, where each instance once used, keeps a reference to the last authenticated subject including all roles

Show

Sebastian Gonzalez Oyuela added a comment - 27/Jul/10 7:59 AM Keep in mind that JBoss keeps a cache of JAAS Login module instances, where each instance once used, keeps a reference to the last authenticated subject including all roles

People

Assignee:

Sebastian Gonzalez Oyuela

Reporter:

Andrew Crowe
Votes:

0

Watchers:

0

Dates

Created:

11/May/10 10:14 AM

Updated:

27/Jul/10 7:59 AM

Resolved:

27/Jul/10 7:56 AM