This is an indication of a ThreadLocal variable being used within the context
of a webapp classloader which did not get cleared out when that application was
stopped. This can lead to PermGen memory errors, as the classloader cannot be
removed. Tomcat does have some logic in it to try and clean
For this type of error you must tuning your apache tomcat for example like this:
-server -Xms2048m -Xmx2048m -XX:PermSize=128m -XX:MaxPermSize=256m
in Environment Variable JAVA_OPTS into catalina.sh or catalina.bat
2012/2/1 James Annesley :
> Tomcat 7.0.25 x64
> RAM= 8GB
> CPU = 8xCPU
> Java = jd
Tomcat 7.0.25 x64
RAM= 8GB
CPU = 8xCPU
Java = jdk1.6.0_25 x64
I am looking at the tomcat instance in visualvm. I have got eclipse open
which takes 1 GB. PermGen is close to max. It ran out of PermGen when I
redeployed.
Is this enough info?
James
-Original Message-
From: Moises Albert
can you tell us your tomcat memory configuration and harware ram, cpu,
type (32 or 64 bits) characteristics???
2012/2/1 James Annesley
>
> Hi,
>
>
>
> I have an XML beans based AXIS 2 1.6.0 stub. After using the client’s UI for
> a short period of time – say a few minutes – having un-deployed th
Hello James,
Thanks for your answer but it doesn't work :(
In fact I change my client code according to your advice:
Options options = sc.getOptions();
options.setProperty(RampartMessageData.KEY_RAMPART_POLICY,
getRampartConfig());
sc.setOptio
