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 210313 - java.net.SocketTimeoutException: connect timed out
Summary: java.net.SocketTimeoutException: connect timed out
Status: RESOLVED FIXED
Alias: None
Product: javascript
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-28 18:53 UTC by John Jullion-ceccarelli
Modified: 2012-09-07 02:13 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 186168

Attachments
stacktrace (2.93 KB, text/plain)
2012-03-28 18:53 UTC, John Jullion-ceccarelli 		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 John Jullion-ceccarelli 2012-03-28 18:53:53 UTC 
This issue was reported manually by pjiricka.
It already has 2 duplicates 


Build: NetBeans IDE Dev (Build EaselCSS-157-on-20120327)
VM: Java HotSpot(TM) Client VM, 22.1-b02, Java(TM) SE Runtime Environment, 1.7.0_03-b05
OS: Windows 7

User Comments:
johnjullion: Run File on HTML file in easel build. Chrome selected as target browser. Chrome already open and plugin installed. First time this session I had run this file.

johnjullion: Ran file in FatJSMobileMvc project in Chrome.




Stacktrace: 
java.net.SocketTimeoutException: connect timed out
   at java.net.DualStackPlainSocketImpl.waitForConnect(DualStackPlainSocketImpl.java:0)
   at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75)
   at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
   at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
   at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157)
Comment 1 John Jullion-ceccarelli 2012-03-28 18:53:59 UTC 
Created attachment 117431 [details]
stacktrace
Comment 2 John Jullion-ceccarelli 2012-03-28 19:33:18 UTC 
After restarting the IDE this error went away.
Comment 3 David Konecny 2012-03-29 22:35:13 UTC 
There is one problem I know of: if a debugging connection from IDE is established to browser and later IDE is closed the browser is unaware that connection was closed. Likely error on our side - we have to do proper clean up. Side effect is that any new connection from IDE to browser will be refused or may time out. Browser shutdown is workaround in the meantime.
Comment 4 John Jullion-ceccarelli 2012-03-29 23:07:42 UTC 
Yes browser shutdown usually fixes the problem.
Comment 5 Martin Entlicher 2012-09-03 08:47:45 UTC 
Yes, we need to explicitly close the connection when NetBeans are shut down.
Comment 6 Martin Entlicher 2012-09-06 12:13:17 UTC 
The external browser is now de-initialized on shutdown of NetBeans.
This exception is quite old, but the external browser should definitely stop debugging the tab using NetBeans plugin.
This is fixed by changeset:   231983:2f4580af5554
http://hg.netbeans.org/main/rev/2f4580af5554
Comment 7 Quality Engineering 2012-09-07 02:13:10 UTC 
Integrated into 'main-golden', will be available in build *201209070001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/2f4580af5554
User: mentlicher@netbeans.org
Log: #210313: Deinitialize the browser tabs on shutdown.