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.
Summary: | java.net.ConnectException at org.netbeans.modules.nativeexecution.api.util.HostInfoUtils.fileExists | ||
---|---|---|---|
Product: | cnd | Reporter: | Exceptions Reporter <exceptions_reporter> |
Component: | execution | Assignee: | Vladimir Kvashin <vkvashin> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | vv159170 |
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 197446 |
Attachments: | stacktrace |
Description
Exceptions Reporter
2013-01-14 20:38:06 UTC
Created attachment 130210 [details]
stacktrace
moved to execution sub-component as dlight is gone from the NetBeans There is no way to protect the code from the connection lost, so will throw exception as it is done now. I'm getting this "red brick message" many times. We should just handle the exception differently. Integrated into 'main-silver', will be available in build *201611100001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/1ac6f1533a1d User: Vladimir Kvashin <vkvashin@netbeans.org> Log: fixed #224873 - java.net.ConnectException at org.netbeans.modules.nativeexecution.api.util.HostInfoUtils.fileExists (transplanted from 081c6acc304aa16e68557f30bda498f3924cafa3) I can't reproduce this random exception in internal NetBeans 8,2 patch 1 build. |