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 57180

Summary:	Content of runtime tab initialized during shutdown
Product:	db	Reporter:	_ rkubacki <rkubacki>
Component:	Code	Assignee:	Andrei Badea <abadea>
Status:	CLOSED FIXED
Severity:	blocker	CC:	issues
Priority:	P3	Keywords:	PERFORMANCE
Version:	4.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:

Description _ rkubacki 2005-03-30 12:01:56 UTC

JDK1.5.0, Solaris, dev build March 22, 2005

The folder instance containing nodes of runtime tab is initialized during
shutdown. This slows down the whole action (it takes ~0.5 sec on my Solaris 10
running on ULTRA 60) as it loads new classes and does a lot of unneceseary
processing to create nodes like: database explorer root node, HTTP server node,
XML catalog node and others. 

I am not sure what triggers this processing as it is runnable in RP -
FolderInstance$ChildrenRefreshRunnnable. Maybe it is related to storing of
runtime tab as a part of winsys.

Comment 1 _ rkubacki 2005-03-30 17:57:06 UTC

Now I see that this is caused by DatabaseModule.close(). It should be more
friendly and do nothing if there is no connection. 

Split of nodes and underlying data can help here.

Comment 2 Andrei Badea 2005-10-14 16:16:55 UTC

I hope this issue is fixed now. After integrating the Database Explorer API
DatabaseModule.close() doesn't do anything with the Runtime tab when it
retrieves the list of connections. But note that if a connection was connected,
calling disconnect() would still initialize the Runtime tab.

Comment 3 Martin Schovanek 2005-11-21 10:22:13 UTC

VERIFIED