This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
After about 30 compiles GlassFish fired an OutOfMemoryError error. I dint't changed application.xml before this error appeared, as is said on forum, just recompiled for many times (have changed code) StandardWrapperValve[RemoteJmxConnectorServlet]: PWC1406: Servlet.service() for servlet RemoteJmxConnectorServlet threw exception java.lang.OutOfMemoryError: PermGen space PWC3989: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError: PermGen space PWC3989: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError: PermGen space PWC3989: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError: PermGen space PWC3989: An exception or error occurred in the container during the request processing java.lang.OutOfMemoryError: PermGen space StandardWrapperValve[RemoteJmxConnectorServlet]: PWC1406: Servlet.service() for servlet RemoteJmxConnectorServlet threw exception java.lang.OutOfMemoryError: PermGen space WEB0756: Caught exception during HTTP processing. java.lang.OutOfMemoryError: PermGen space StandardWrapperValve[RemoteJmxConnectorServlet]: PWC1406: Servlet.service() for servlet RemoteJmxConnectorServlet threw exception java.lang.OutOfMemoryError: PermGen space
Heavy system! Reboot of IDE didn't helped. I have had to reboot the whole computer! :D
Reassigning.
this looks pretty serious... I will dig into it.
please describe the application that you are working on when this happens... about how big is it (as a deployable archive)? what kind of app is it... war or ear? what java ee version is it code against ee 5, ee 6, j2ee 1.4? That kind of info will help me reproduce the problem.
1. didn't understand exactly a question, but - size of "war" folder is 1,02 MB (1.073.152 bytes), - in debug mode it is shown 65,6 / 90,1 Mb, - in Servers > Glassfish v2.1 > Applications > Web applications > my project > properties - haven't found any records about size. 2. war. The project is Spring MVC + GWT framework. 3. JDK 1.6.0_12
is this gf v3 or gf v2.1?
2.1
I tried to reproduce this on Solaris... but was not able to do it. I created a web app project that uses the Spring MVC framework. I created a couple of Spring MVC artifacts in the project. I used the Deploy item on the project's right-click menu about 40 times. I changed strategy.. I started making minor changes in one of the Spring MVC artifact's source files and saving the change. This put 'Deploy on Save' through the test. I did 40 redeployments, triggered by an edit/save in the source code for the project. Still I did not see a OOM. I will try my Windows Vista box tonight.
This is a very old and annoying issue since glassfish v1 and still persisting. It happens after many redeploys of EAR or WAR in short period. Deploy on save just speed up the process. The only workaround found is to increase MaxPermSize in jvm options on glassfish. And one more thing, you don't have to restart you computer, just have to kill java process of glassfish, because of PermGen it can't be stoped by asadmin command.
I think this a variation of famous PermGen OOME. This is related to JVM design and the way how some frameworks manipulate/generate classes. I doubt it is related to NetBeans. Perhaps GF could do something about that. One of many blogs on this: http://www.jroller.com/agileanswers/entry/preventing_java_s_java_lang
*** Issue 165341 has been marked as a duplicate of this issue. ***
OK. There is not much the plugin can 'do' about this, since the Permgen issue is really a bug in the way the server interacts with your app. There is an open issue for v2.1 for this problem: https://glassfish.dev.java.net/issues/show_bug.cgi?id=5104 There is a similar issue open against v3: https://glassfish.dev.java.net/issues/show_bug.cgi?id=6082. After reading though both issues, it seems like you may have 'more joy' (== fewer PermGen issues) by trying to use recent builds of GF v3... See https://glassfish.dev.java.net/issues/show_bug.cgi?id=6082#desc25 and https://glassfish.dev.java.net/issues/show_bug.cgi?id=6082#desc27 Since the plugin cannot do much about the problem, I am going to close this issue as INVALID (in the context of this issue tracker and code base), there are entries in the trackers where this issue should be tracked. I opened issue 172518 to track an enhancement to the Stop action in the v2 plugin. I also opened issue 172518 for the v3 plugin