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 142639

Summary: [65cat] org.netbeans.api.db.explorer.DatabaseException: Communications link failure Last packet sent to the server was 9 ms ago.
Product: db Reporter: sunbiz <sunbiz>
Component: CodeAssignee: John Baker <jbaker>
Status: RESOLVED DUPLICATE    
Severity: blocker CC: romanmostyka
Priority: P3    
Version: 6.x   
Hardware: All   
OS: All   
URL: http://statistics.netbeans.org/exceptions/detail.do?id=85409
Issue Type: DEFECT Exception Reporter: 85409
Bug Depends on: 143837    
Bug Blocks:    
Attachments: stacktrace

Description sunbiz 2008-08-01 20:08:51 UTC
Build: NetBeans IDE Dev (Build 080731)
VM: Java HotSpot(TM) Client VM, 11.0-b12, Java(TM) SE Runtime Environment, 1.6.0_10-beta-b25
OS: Windows Vista, 6.0, x86

User Comments: 
Connection to database was terminated due to network failure and tried to view tables during network failure.

Stacktrace: 
org.netbeans.api.db.explorer.DatabaseException: Communications link failure

Last packet sent to the server was 9 ms ago.
        at org.netbeans.modules.db.explorer.infos.TableListNodeInfo.initChildren(TableListNodeInfo.java:110)
        at org.netbeans.modules.db.explorer.infos.DatabaseNodeInfo.getChildren(DatabaseNodeInfo.java:689)
        at org.netbeans.modules.db.explorer.nodes.DatabaseNode$DatabaseNodeChildFactory.createKeys(DatabaseNode.java:382)
        at org.openide.nodes.AsynchChildren.run(AsynchChildren.java:147)
        at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572)
        at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997)
Comment 1 sunbiz 2008-08-01 20:09:01 UTC
Created attachment 66347 [details]
stacktrace
Comment 2 David Vancouvering 2008-08-04 23:00:51 UTC
This is the expected failure if the network is down.  What would you like NB to do differently?
Comment 3 David Vancouvering 2008-08-15 20:34:35 UTC
Looks like we should test to see if the connection is valid before refreshing the table list.  Similar to Issue 143798.
Comment 4 David Vancouvering 2008-09-09 01:03:01 UTC
I'll work on this John, it's the same as 146442

*** This issue has been marked as a duplicate of 146442 ***