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.
I notice that deploy web app using Sun's app server usually fails after couple times. This means I have to stop and start the app server often. This is a long and frustrating development experience. The problem usually out of memory exception. Some folk may say this has something to do with the appserver versus the IDE, to me as a developer, I think if I can be productive and not dealing with this is the best. I don't want to offend people here, but this is very frustrated experience, and almost unacceptable for any development standard these day.
Reassigning to sunappserv for evaluation
please update this issue with the platform and os info. it makes it easier to start working on this issue
Which framework do you use in your web app? Strut? Can you tell if the memory issue is really from the App server and not the application? Thanks for sharing more info with us.
The web app uses spring, struts, tile, hibernate. I am not sure where the memory problem comes from, but running the application alone does not have memory problem. Only on undeploy and redeploy. Also, it does not need to do alot in the app to have this problem. Just go to the application's first page and then deploy. Repeat this couple times and the problem shows up.
The bug is not in the netbeans plugin, but in the server. See https://glassfish.dev.java.net/issues/show_bug.cgi?id=539 Or if this is the case, in the strut framework. Can you confirm?
To follow up on this, this has to be tracked on the App server side, not the NetBeans product. Please, see the referred bug and add your comments there You can also file new bugs on AS side, and the best is to give a reproducible case. So I mark this bug as WONTFIX. This is for NetBeans side, of course since it cannot be fixed on this side. On the App Server side, I am sure it will be addressed (if you provide the correct info, including the version you are using. Thanks.
fyi, we were able to reproduce a WebappClassLoader leak on GlassFish 9.0peur1 by simply deploying and undeploying JSPWiki (which bundles both commons-logging and log4j). Each redeploy would add another (leaking) WebappClassLoader instance to the heap. This was with jdk1.5.0_06. After upgrading to jdk1.5.0_07 or jdk1.5.0_08, the leak went away. This points to a bug in the VM's GC as the root cause of the leak, which was also supported by the "other gc root" box in the reference graphs for the leaking WebappClassLoader instances in the mem profiler we were using. See http://forums.java.net/jive/thread.jspa?messageID=150129𤩱 for details on the JSPWiki leak. Could everyone who has reported OutOfMemoryError problems and filed related bugs please make sure that your appserver is running against jdk1.5.0_07 or jdk1.5.0_08?