vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On 1/8/08 7:49 AM, "Guillaume Cottenceau" <gc@mnc.ch> wrote: > Håkan Jacobsson <hakan.jacobsson 'at' relevanttraffic.com> writes: > >> javax.ejb.EJBException: java.lang.RuntimeException: >> java.lang.OutOfMemoryError: >> PermGen space >> >> We start JBoss with -Xms2048m -Xmx2048m arguments, which , as I understand >> it, >> is the maximum heap size we can use > > that's not related to the mx. you have to increase the permanent > generation (mnore information in java gc documentation). Unfortunately, in my experience, increasing the PermGen space only delays the problem. The underlying issue seems to be related to classloading/unloading when "hot deploying" applications (tomcat, glassfish, jetty, etc.). When a new version of the class is deployed, the old class is unloaded, but apparently doesn't release its PermGen space. Mike ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster |