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 166891 - Sybase "Connection already closed" exception doesn't clear the DB-tree
Summary: Sybase "Connection already closed" exception doesn't clear the DB-tree
Status: NEW
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P4 blocker (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-11 03:12 UTC by mabe02
Modified: 2013-08-01 12:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mabe02 2009-06-11 03:12:27 UTC
Using NetBeans 6.7 RC1:
When using the Sybase JDBC driver (jconn3.jar) to connect to a Sybase server, and leaving the connection unused for a
while (varies depending on the server configuration I guess), the server will automatically close the connection and the
next time a JDBC command (such as SQL) is issued, it replies with a "Connection already closed"-exception.

I had an open connection in Netbeans (on Service tab, under the Databases node) unused for about 5 minutes. Then I
Right-clicked and chose "Disconnect". The server had already closed my connection and NetBeans informed me of the
Exception via a red icon in the bottom right corner. However, the tree under the server node  was still fully populated
and the icon was still that of a connected connection. The right click menu was changed to enable Connect and disable
Disconnect though. I guess somewhere in the code, maybe the Connection.close() isn't guarded for a SQLException and
therefor never clears the tree. 

Or maybe it's supposed to work like this.