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.

Bug 48877

Summary:	out of memory exceptions
Product:	javaee	Reporter:	_ ludo <ludo>
Component:	Code	Assignee:	Chris Webster <cwebster>
Status:	VERIFIED FIXED
Severity:	blocker	CC:	issues
Priority:	P2	Keywords:	PERFORMANCE
Version:	4.x
Hardware:	PC
OS:	Windows ME/2000
Issue Type:	DEFECT	Exception Reporter:
Bug Depends on:	49975, 50050, 50182, 50444
Bug Blocks:

Description _ ludo 2004-09-11 17:03:34 UTC

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.

Comment 1 Petr Jiricka 2004-09-13 09:58:00 UTC

Ludo, is the j2eeserver category intentional? Do you know that this is
a problem in j2eeserver, or is this just a placeholder?

Comment 2 _ ludo 2004-09-13 15:05:37 UTC

wrong cat. Sorry

Comment 3 _ ludo 2004-09-29 19:18:48 UTC

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.

Comment 4 _ ludo 2004-10-03 00:12:03 UTC

Chis has started the analysis. So far, 2 or 3 memory issues have been
found. Waiting a few days for more before the integration.

Comment 5 Chris Webster 2004-10-11 22:37:01 UTC

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.

Comment 6 Petr Blaha 2004-10-13 10:45:15 UTC

Move issues from temprorary component.

Comment 7 Petr Blaha 2005-01-20 08:38:29 UTC

I can't reproduce it in Build 20050118. I'm marking as verified.