Yeah, more specifically, something must be using a static somewhere. I
know that commons logging does this, for example. But, according to
them, it's not actually their problem, because people shouldn't be
installing common libraries in tomcat's folders, they should be in
WEB-INF/lib.
http://wiki.apache.org/commons/Logging/UndeployMemoryLeak
If everything you use is in WEB-INF/lib, this can't happen because all
the classes would get unloaded, static or otherwise. But, when they are
shared, such as in tomcat/lib, it can become a problem.
I haven't personally seen this problem with CAS, and I've redeployed my
context dozens of times. But, then again, as a developer I only run CAS
on a stock tomcat download.
On 13-07-25 06:35 AM, Marvin S. Addison wrote:
Has anyone else seen such behavior?
See it all the time. The root cause is dangling object references that
pin the parent class loader and all the classes it loaded on startup.
For non-trivial apps that is typically a lot of data. Since class
definitions are placed in the PermGen slot of the JVM, it quickly fills
up on repeated Webapp deploys. Increasing PermGen size only delays the
inevitable.
This comes up occasionally but it's genuinely a difficult problem. It is
feasible to track down all the places where we might leak resources
(e.g. thread locals) in CAS, but the problem is fairly intractable when
considering the myriad libraries on which CAS depends. The Spring
Framework and Hibernate are two huge dependencies; there are many
others. It's easier to simply deploy CAS in a Tomcat instance by itself
and restart the container as part of redeployment. I believe most CAS
deployers do this; we certainly do.
M
--
Trenton D. Adams
Senior Systems Analyst/Web Software Developer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!
--
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
