Hello,
We have a CAS server using JAAS + Kerberos to authenticate users against
Active Directory. We started seeing OutOfMemoryErrors with the default
Xmx (of 64m) which we have since bumped up to 256m. We haven't had
OutOfMemoryErrors since then, but the memory usage keeps rising.
I've hooked up JProfiler to try and see where the memory is going, and
noticed that it goes up with each request, and running the garbage
collector (via System.gc()) doesn't reclaim many of the objects. I'm
sure we just have a configuration error of sorts, but I've spent a few
days and can't seem to figure it out.
JProfiler tells me that after a few requests (500 or so), we have an
enormous number of LinkedHashMap$Entry objects, as well as
java.security.Provider$ServiceKey, java.security.Provider$Service, and
HashMap$Entry instances.
I've also noticed that instances of com.sun.crypto.provider.SunJCE go up
by 2 per request, and don't get reclaimed with garbage collection.
JProfiler's cumulative allocations point to
javax.security.auth.login.LoginContext.login() method, but I've checked
out the code and stepped through it with a debugger, but can't see
anything wrong (no creation of instances that would be uncollectable by
the gc).
If it helps, here's our jaas.conf file:
CAS {
com.sun.security.auth.module.Krb5LoginModule required
client=TRUE debug=FALSE useTicketCache=FALSE;
};
I'm going to try to setup CAS to use the LDAP authentication handler to
see if the problem is strictly JAAS related.
Has anyone seen issues like this before?
Thanks in advance!
Brad Cupit
Louisiana State University - UIS
e-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
office: 225.578.4774
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
