After killing my previous copy of the IDE, I 
started NetBeans again.

There was a long enough delay that I thought 
something had gone wrong, and brought up the 
task manager to kill the process.

Then the stacktrace below appeared on the 
console (not for release builds, I presume), and
the splash screen came up and the IDE started.


If we're going to take this approach to avoid 
two instances running with the same userdir, 
there needs to be some UI - splash screen or 
something, or the timeout period needs to be 
shorter, or both.

Question:  Would it be possible/possibly harmful 
to do this socket check asynchronously, and have 
it simply kill the JVM one way or another if the 
exception isn't thrown?  If we don't do any file 
*writing* on second and later startups on the 
same user directory, that would probably do the 
trick.  I suppose you don't know what modules 
will want to do on startup, but if you could 
guarantee that everything before that point 
would not cause any userdir writes, at least 
that part of startup could be done 
asynchronously.

The one tricky thing would probably be ide.log; 
it may not be worth it, but the current delay 
with no UI just looks like something's broken.

------

java.net.ConnectException: Connection timed out: 
connect
        at java.net.PlainSocketImpl.socketConnect
(Native Method)
        at java.net.PlainSocketImpl.doConnect
(PlainSocketImpl.java:305)
        at 
java.net.PlainSocketImpl.connectToAddress
(PlainSocketImpl.java:171)
        at java.net.PlainSocketImpl.connect
(PlainSocketImpl.java:158)
        at java.net.Socket.connect
(Socket.java:452)
        at java.net.Socket.connect
(Socket.java:402)
        at java.net.Socket.<init>
(Socket.java:309)
        at java.net.Socket.<init>
(Socket.java:153)
        at org.netbeans.CLIHandler.initialize
(CLIHandler.java:366)
        at org.netbeans.CLIHandler.initialize
(CLIHandler.java:239)
        at org.netbeans.Main.main(Main.java:100)