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.
1. Installed full Standard NetBeans (Java IDE + WebPack + Mobility Pack + GlassFish). 2. Start IDE. 3. Select 'Runtime' tab and expand 'Databases' node. 4. Rightclick default DB (bound to GlassFish and added by default to 'Databases' node) and click 'Connect'. Result: Error message about opening socket appears and connection fails. See screenshot for full text of error.
Created attachment 41256 [details] Screeshot
On which JDK? Is Java DB registered? Look in Tools - Options - Advanced Options - Server and External Tool Settings - Java DB Location. If registered, can you start it manually using Tools - Java DB Database - Start Java DB Server?
One thought, I've had this happen when the Java DB network server is already running. I also get this sporadically for reasons that are unclear to me, when I specifically see Java DB running in the output window at the bottom. Then when I try to connect again it works.
Please check ports used by your system % netstat | grep 1527 if 1527 is in use then, assuming this port was reserved by Derby, you may have to kill the jdbc java process
Please check ports used by your system % netstat | grep 1527 if 1527 is in use then, assuming this port was reserved by Derby, you may have to kill the jdbc java process. I'm marking as INCOMPLETE until more info is provided
Reboot, reinstall IDE and everything works fine. Reinstall second time, everything also works fine.
I saw this issue today on another computer, I want to investigate more.
I don't see a way how this can occur except for the Java DB server taking longer to start than 5 seconds. I added some logging, so now if this happens there will be a message in the log. If you still happen to encounter the issue, please look in the message log for something like: WARNING [org.netbeans.modules.derby.RegisterDerby]: Derby server failed to start in 5000 ms and post a commment about it to this issue. I also think that if the server fails to start in 5 seconds, we should display a dialog asking the user whether to wait more instead of just silently giving up waiting.
Adding logging. Checking in src/org/netbeans/modules/derby/RegisterDerby.java; /cvs/db/derby/src/org/netbeans/modules/derby/RegisterDerby.java,v <-- RegisterDerby.java new revision: 1.24; previous revision: 1.23 done
*** Issue 97648 has been marked as a duplicate of this issue. ***
Just reproduced the error when trying to connect to Derby while the initial scan was running. Got the message I mentioned in desc9. It seems sometimes Derby fails to start in 5000 ms.
Fixed by introducing a confirmation dialog informing that the server did not start in 5 seconds and asking whether to wait for another 5 seconds. Checking in src/org/netbeans/modules/derby/Bundle.properties; /cvs/db/derby/src/org/netbeans/modules/derby/Bundle.properties,v <-- Bundle.properties new revision: 1.20; previous revision: 1.19 done Checking in src/org/netbeans/modules/derby/ExecSupport.java; /cvs/db/derby/src/org/netbeans/modules/derby/ExecSupport.java,v <-- ExecSupport.java new revision: 1.5; previous revision: 1.4 done Checking in src/org/netbeans/modules/derby/RegisterDerby.java; /cvs/db/derby/src/org/netbeans/modules/derby/RegisterDerby.java,v <-- RegisterDerby.java new revision: 1.26; previous revision: 1.25 done Checking in src/org/netbeans/modules/derby/StartAction.java; /cvs/db/derby/src/org/netbeans/modules/derby/StartAction.java,v <-- StartAction.java new revision: 1.9; previous revision: 1.8 done
Verified with build 070903.