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 an hour or so of using J2EE features: ejb, web services and web services client, there is a out of memory exception. Cannot continue further. This has to be fixed for EA1, as well as a test case testing this long run scenario.
Ludo, is the j2eeserver category intentional? Do you know that this is a problem in j2eeserver, or is this just a placeholder?
wrong cat. Sorry
Some scenarios to reproduce this state... Usually, it's at the end of a demo after 50 minutes of usage... 1/ create web app 2/ add web service, add operation 3/ deploy, access the WS wsdl url (...?wsdl) 4/ (when it works) add a service in the registry (run time tab), as see it. Try the test method if you can. 5/ create ejb module 6/ add ejb 7/ see ejb-jar.xml and sun-ejb-jar.xml 8/ compile 9/ add business method, compile or deploy 10/ refactor rename the EJB impl class. See the impact on ejb-jar.xml in the xml editor 11/ From 2/ web service java code, try to popup call ejb and add the one created 12/ see the web.xml file 13/ create j2ee application. Try to add the web app and the ejb module 14/ at this stage, if all the steps did not explode, you should start seeing soem OOM exceptions...Compile the J2EE app... 15/repeat from 1/ until OOM strikes.
Chis has started the analysis. So far, 2 or 3 memory issues have been found. Waiting a few days for more before the integration.
In evaluating this bug several issues were identified and resolved in the j2ee modules: * web, ejb, and app projects had a leak in the customizer. The leak was caused because of a member variable in the Customizer Provider. * web service registry had a thread leak where a thread was not completing when a service was added to the registry. * Fixed a memory related issue (not leak though) where the comparator for the ejb module was causing an entire new set of nodes to be created anytime a change was made to the deployment descriptor. More of a performance issue. Several netbeans issues were uncovered as well which involved a memory leak when creating a new project and creating a new java related class. I have added these bugs to the depends on list.
Move issues from temprorary component.
I can't reproduce it in Build 20050118. I'm marking as verified.