On Sat, 08 Sep 2012 11:51:28 +0200, Casper Bang <[email protected]>
wrote:
Yes, it was not clear from the discussion that the problem is a design
issue within the JVM and that removing PermGen really just pushes the
problem to another generation. I'd love a deep dive into this issue by
the
The Posse and/or guests. It's a little pathetic/scary that if you
redeploy
a Java app one too many times to a container, it may blow up (typically
stop responding at all and needing a kill -9). It makes me question the
whole container aspect and instead deploy with
embedded light-weight containers (Jettt/Grizzly).
I'm using extensively Jetty (6) for more than one year for all my
websites. I had to increment PermGen as well (explicit PG OOM error). I
don't have other PG problems related to redeploying since I seldom
redeploy (and at the moment I have another problem related to a periodical
explosion of sockets in the CLOSE_WAIT state that force me to restart
jetty).
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
[email protected]
http://tidalwave.it - http://fabriziogiudici.it
--
You received this message because you are subscribed to the Google Groups "Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
