Out of permgen memory when re-deploying applications

We are experiencing out of memory errors when re-deploying applications to running GSCs. I have done some research and found that the likely culprit is CGLIB generating dynamic class definitions in permgen memory, which do not get unloaded when the app is undeployed. So I don't think this is a gigaspace problem (in fact it seems to affect apps deployed on different containers - tomcat, jboss, to name a couple). However it is a problem we have to solve.

So far, the only long-term solution I can come up with is to restart the GSC with every (few) deployment. I wonder if anyone else can come up with something better? For us, increasing the permgen space or switching from Sun's jvm to BEA's jrockit are not long-term solutions.

Also, does anyone know when the gs (commandline) commands for stopping the GSC/GSM will be released? And will they be integrated into the maven openspaces plugin?

Thanks,

David h4. Attachments

[2009-10-30~08.44-gigaspaces-gsc-BROLGA-3972.log|/upfiles/13759704789623269.txt]

[2009-10-30~08.44-gigaspaces-gsm_lh-BROLGA-2480.log|/upfiles/13759704785443869.txt]

{quote}This thread was imported from the previous forum. For your reference, the original is [available here|http://forum.openspaces.org/thread.jspa?threadID=3297]{quote}

asked 2009-10-29 13:39:15 -0600

dsmain gravatar image

updated 2013-08-08 09:52:00 -0600

jaissefsfex gravatar image
edit retag flag offensive close merge delete