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.
This issue was reported manually by vv159170. It already has 1 duplicates Build: NetBeans IDE 7.3 Beta (Build 201210011125) VM: Java HotSpot(TM) Client VM, 23.3-b01, Java(TM) SE Runtime Environment, 1.7.0_07-b11 OS: Windows 7 Stacktrace: com.jcraft.jsch.JSchException: Session.connect: java.net.SocketTimeoutException: Read timed out at com.jcraft.jsch.Session.connect(Session.java:507) at org.netbeans.modules.nativeexecution.jsch.JSchChannelsSupport.startNewSession(JSchChannelsSupport.java:244) at org.netbeans.modules.nativeexecution.jsch.JSchChannelsSupport.connect(JSchChannelsSupport.java:206) at org.netbeans.modules.nativeexecution.jsch.JSchConnectionTask.connect(JSchConnectionTask.java:126) at org.netbeans.modules.nativeexecution.jsch.JSchConnectionTask.access$000(JSchConnectionTask.java:62) at org.netbeans.modules.nativeexecution.jsch.JSchConnectionTask$1.call(JSchConnectionTask.java:88)
Created attachment 126677 [details] stacktrace
http://hg.netbeans.org/cnd-main/rev/37c9dd25207c
Integrated into 'main-golden', will be available in build *201210310001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/37c9dd25207c User: Andrew Krasny <akrasny@netbeans.org> Log: #220970 - com.jcraft.jsch.JSchException: Session.connect: java.net.SocketTimeoutException: Read timed out The fix is not to use Exceptions.printStackTrace(e) in case IOException while connection. To make things easier a method connect() that throws no exceptions is introduced. Fixed several places where this pattern suits.