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 147246 - [65cat] org.netbeans.api.db.explorer.DatabaseException: No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: ** BEGIN NESTED EXCEPTION ** com.m
Summary: [65cat] org.netbeans.api.db.explorer.DatabaseException: No operations allowed...
Status: RESOLVED DUPLICATE of bug 146442
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Vancouvering
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-15 10:56 UTC by rohitbrai
Modified: 2008-09-17 19:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 105517

Attachments
stacktrace (4.65 KB, text/plain)
2008-09-15 10:57 UTC, rohitbrai 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rohitbrai 2008-09-15 10:56:59 UTC 
Build: NetBeans IDE Dev (Build 200809100201)
VM: Java HotSpot(TM) Client VM, 1.6.0_01-b06, Java(TM) SE Runtime Environment, 1.6.0_01-b06
OS: Windows XP, 5.1, x86

User Comments: 
1. Connect to a MySQL Server on remote host
2. Create connection to a table
3. Open the connection
4. Click to expand "Tables"

Stacktrace: 
org.netbeans.api.db.explorer.DatabaseException: No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error:


** BEGIN NESTED EXCEPTION ** 

com.mysql.jdbc.exceptions.jdbc4.CommunicationsException
MESSAGE: Communications link failure

Last packet sent to the server was 0 ms ago.

STACKTRACE:

com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

Last packet sent to the server was 0 ms ago.
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
	at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074)
	at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2985)
	
        at org.netbeans.modules.db.explorer.infos.TableListNodeInfo.initChildren(TableListNodeInfo.java:113)
        at org.netbeans.modules.db.explorer.infos.DatabaseNodeInfo.loadChildren(DatabaseNodeInfo.java:710)
        at org.netbeans.modules.db.explorer.infos.DatabaseNodeInfo.getChildren(DatabaseNodeInfo.java:698)
        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)
Comment 1 rohitbrai 2008-09-15 10:57:05 UTC 
Created attachment 69854 [details]
stacktrace
Comment 2 David Vancouvering 2008-09-15 16:59:09 UTC 
This is another case where if we validate the connection before we try to use it we should be able to catch this and
reconnect.  At any rate we should be raising it as a dialog rather than as a stack trace.
Comment 3 David Vancouvering 2008-09-17 19:45:03 UTC 

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