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 254890 - NullPointerException at org.netbeans.modules.nativeexecution.jsch.JSchChannelsSupport.releaseChannel
Summary: NullPointerException at org.netbeans.modules.nativeexecution.jsch.JSchChannel...
Status: NEW
Alias: None
Product: cnd
Classification: Unclassified
Component: execution (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: ilia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-01 06:12 UTC by Exceptions Reporter
Modified: 2017-07-04 15:24 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 219568

Attachments
stacktrace (1.03 KB, text/plain)
2015-09-01 06:12 UTC, Exceptions Reporter 		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 Exceptions Reporter 2015-09-01 06:12:33 UTC 
This issue was reported manually by alexvsimon.
It already has 1 duplicates 


Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.76-b04, Java(TM) SE Runtime Environment, 1.7.0_76-b13
OS: Windows 7

User Comments:
GUEST: NA




Stacktrace: 
java.lang.NullPointerException
   at org.netbeans.modules.nativeexecution.jsch.JSchChannelsSupport.releaseChannel(JSchChannelsSupport.java:297)
   at org.netbeans.modules.nativeexecution.api.util.ConnectionManager$ConnectionManagerAccessorImpl.closeAndReleaseChannel(ConnectionManager.java:615)
   at org.netbeans.modules.nativeexecution.NbRemoteNativeProcess.waitResultImpl(NbRemoteNativeProcess.java:102)
   at org.netbeans.modules.nativeexecution.NbNativeProcess.waitResult(NbNativeProcess.java:197)
   at org.netbeans.modules.nativeexecution.AbstractNativeProcess$1.call(AbstractNativeProcess.java:165)
   at org.netbeans.modules.nativeexecution.AbstractNativeProcess$1.call(AbstractNativeProcess.java:157)
Comment 1 Exceptions Reporter 2015-09-01 06:12:35 UTC 
Created attachment 155790 [details]
stacktrace
Comment 2 ilia 2017-07-04 13:47:45 UTC 
NPE here: sessions.get(s).incrementAndGet(); (rev 276295)
Comment 3 ilia 2017-07-04 15:24:30 UTC 
This is a bug, not just "bad logging"

NPE means that someone called releaseChannel ignoring the fact a corresponding session couldn't start (and thus ConcurrentHashMap<Session, AtomicInteger> doesn't contain this session).