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 48000 - Deleting closed project - Failed to lookup configuration for Tomcat5
Summary: Deleting closed project - Failed to lookup configuration for Tomcat5
Status: CLOSED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P4 blocker (vote)
Assignee: Pavel Buzek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-26 14:58 UTC by zikmund
Modified: 2006-03-24 10:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log with several exceptions (58.18 KB, text/plain)
2004-08-26 14:59 UTC, zikmund
Details

Note You need to log in before you can comment on or make changes to this bug.
Description zikmund 2004-08-26 14:58:24 UTC
Build 200408251800

1) Start IDE with new userdir
2) Create WebModule
3) Close WebModule
4) Delete WebModule's directory on disk
5) Switch back to IDE
6) Wait a moment (less than 10 seconds)
7) ERROR:
Scanning dialog appears (not fully visible)
immediately followed by EXCEPTION -- see attached
IDE log (scanning dialog disappears almost
immediately).

The begin of exception:

Annotation: Failed to lookup configuration for
Tomcat5 in
org.netbeans.modules.web.project.ProjectWebModule@e17436

java.lang.IllegalStateException: New
J2eeProviderImplementation needs to override this
method!

Notice: it doesn't break functionality, but it
appears also if you do some work between closing
project and it's deleting -- in that case you are
not sure why this exception appears and what
impact will it have on your work.
Comment 1 zikmund 2004-08-26 14:59:01 UTC
Created attachment 17163 [details]
IDE log with several exceptions
Comment 2 Nam Nguyen 2004-08-26 18:02:39 UTC
From the stack its seems that after project closing ProjectWebModule
object is still around listening to disk file change event through
FileChangeSupport and ProjectProperties.  I am not sure this is just
left-over or intentional as required by project system.  Adding Jesse
G for opinion.
Comment 3 Jesse Glick 2004-08-27 03:04:33 UTC
Projects are not destroyed when they are "closed"; just removed from
the list shown in the GUI. They are eligible for collection.
Comment 4 Nam Nguyen 2004-08-27 21:38:44 UTC
Pavel, I think this symptom is caused by project objects still
listening on project file change event through project util.  Would
your work on memory leak also fix this issue?
Comment 5 Pavel Buzek 2004-09-17 21:44:28 UTC
Karle, can you check this again? I did what you describe and I only
see exceptions in log but no exception message is displayed to the user. 
If this is correct I am downgrading to P5.

In any case the exception is harmless.
When I am testing now I do not see the DDDataObject involved, only the
project support classes listen to file changes and fire events on
objects that are not GCed yet.
Comment 6 Pavel Buzek 2005-02-22 01:01:27 UTC
cannot reproduce, marking as fixed (abadea did more fixes for closed
projects recently..)
Comment 7 zikmund 2005-02-24 17:26:21 UTC
Verified.