Thanks for the advice.
Would set Jarskipping break any web apps (non of them using servlet 3.0
features)?
It would have helped if there is a v6 compatible setting for this.
There are quite a few jar skip setting. is there a way to set a single
param
all web apps are non-3.0 apps?
On 10/26/2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ted,
On 10/25/12 7:24 PM, Ted Smith wrote:
> After upgrading to 7, deploying a new war file often results in
> PermGen error, much more often than in 6.(with identical JVM
> settings) I have tried all those JVM settings for perm memory but
> no help.
Exception in thread "http-bio-7070-exec-31" java.lang.OutOfMemoryError:
PermGen space
at java.lang.Throwable.getStackTraceElement(Native Method)
at java.lang.Throwable.getOurStackTrace(Throwable.java:591)
at java.lang.Throwable.printStackTrace(Throwable.java:510)
a
I am running tomcat 7.0.29, JDK 6.0.30
-XX:MaxPermSize=256m is one of the settings I tried but no help
and others settings that could be found googling.
it occurred in 6 as well, but suddently so often after upgrading to 7
I am curious how many on this list are having the similar issues,
i.e.,
Can you post the exact error message you are seeing and what your JVM
settings are when you get that error?
Warm Regards,
Jordan Michaels
On 10/25/2012 04:24 PM, Ted Smith wrote:
Hello:
After upgrading to 7, deploying a new war file often results
in PermGen error, much more often than in 6.(w
> After upgrading to 7, deploying a new war file often results
> in PermGen error, much more often than in 6.(with identical JVM settings)
> I have tried all those JVM settings for perm memory but no help.
"All those JVM settings for perm memory" - could you share which
settings you have tried, an
Hello:
After upgrading to 7, deploying a new war file often results
in PermGen error, much more often than in 6.(with identical JVM settings)
I have tried all those JVM settings for perm memory but no help.
Is there any way to reduce the chance of PermGen errors?
such as how deployment should be
