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.
Build: NetBeans IDE Dev (Build 2012-04-01_21-03-54 ) VM: Java HotSpot(TM) 64-Bit Server VM, 20.6-b01, Java(TM) SE Runtime Environment, 1.6.0_31-b05 OS: Windows 7 User Comments: GUEST: persistence class not created jc0966: Following tutorial http://www.netbeans.org/kb/docs/ide/mysql.html At Step of Section "Using the SQL Editor"/ Stacktrace: java.lang.IllegalStateException: This connection is not added to the ConnectionManager. at org.netbeans.api.db.explorer.ConnectionManager.showConnectionDialog(ConnectionManager.java:352) at org.netbeans.modules.db.mysql.actions.ConnectAction$1.connectionsChanged(ConnectAction.java:129) at org.netbeans.modules.db.explorer.ConnectionList.fireListeners(ConnectionList.java:166) at org.netbeans.modules.db.explorer.ConnectionList.access$000(ConnectionList.java:71) at org.netbeans.modules.db.explorer.ConnectionList$1.resultChanged(ConnectionList.java:102) at org.openide.util.lookup.ProxyLookup$1Notify.run(ProxyLookup.java:181)
Created attachment 117637 [details] stacktrace
*** Bug 210561 has been marked as a duplicate of this bug. ***
Symptoms like issue 209797.
Quoted from issue 209788: This bug causes some fails in NBQE automated tests. Test started to fail between 7.3.2012 and 20.3.2012. Unfortunately i have no accurate time.
I don't remember the exactly steps, but I have some databases already created at a Java DB instance. So, I started the IDE, started the Java DB from Services | Databases | Java DB > Start... So, I tried to connect to an already created database which hasn't yet a connection listed at Services | Databases. So, my guest is that the error happens because something believe that this database is already listed there.
Probably caused by recent changes in lookup, reassigned to platform/util. A step to reproduce - just run db/test/org.netbeans.modules.db.explorer.DatabaseConnectionTest
*** This bug has been marked as a duplicate of bug 210279 ***