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 147435 - [65cat] [65cat]org.netbeans.api.db.explorer.DatabaseException: No current connection.
Summary: [65cat] [65cat]org.netbeans.api.db.explorer.DatabaseException: No current con...
Status: VERIFIED FIXED
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-17 01:41 UTC by alcmontejo
Modified: 2008-09-22 11:04 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 113380

Attachments
stacktrace (3.42 KB, text/plain)
2008-09-17 01:41 UTC, alcmontejo 		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 alcmontejo 2008-09-17 01:41:40 UTC 
Build: NetBeans IDE Dev (Build 200809151401)
VM: Java HotSpot(TM) Client VM, 1.6.0_02-b06, Java(TM) SE Runtime Environment, 1.6.0_02-b06
OS: Windows XP, 5.1, x86

User Comments: 
Occurs when I click the node of the JavaDB database

Stacktrace: 
org.netbeans.api.db.explorer.DatabaseException: No current connection.
        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 alcmontejo 2008-09-17 01:41:50 UTC 
Created attachment 69995 [details]
stacktrace
Comment 2 alcmontejo 2008-09-17 03:28:16 UTC 
I believe this is P2
Comment 3 David Vancouvering 2008-09-17 17:38:34 UTC 
I'm guessing this happens not every time, but after you change a property on the database, such as the URL or the username?

I am pretty sure this is fixed after my fix to issue 146442.  I just pushed that change, it should show up in tonight's
nightly build.  Can you please see if you still get this issue with tomorrow's nightly build?
Comment 4 David Vancouvering 2008-09-17 17:39:17 UTC 
Sorry, Rob, I didn't mean to assign that to you.
Comment 5 Andrei Badea 2008-09-19 17:44:42 UTC 
Also #daf7dbe0cf33 should have helped with this. I believe this is fixed, so closing. Please reopen if you can still
reproduce it.
Comment 6 Roman Mostyka 2008-09-22 10:43:22 UTC 
alcmontejo, can You verify that this issue was really fixed, please?
Comment 7 alcmontejo 2008-09-22 11:04:02 UTC 
I am currently using Build 200809211401, this is issue was verified fixed . Thank you very much.