[jbosstools-issues] [JBoss JIRA] (JBIDE-21707) NullPointerException in JobResultFuture

[Fred Bricon (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-21707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon reassigned JBIDE-21707:
-----------------------------------

    Assignee: Viacheslav Kabanovich


> NullPointerException in JobResultFuture
> ---------------------------------------
>
>                 Key: JBIDE-21707
>                 URL: https://issues.jboss.org/browse/JBIDE-21707
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: common/jst/core, openshift
>    Affects Versions: 4.3.1.Beta2
>            Reporter: Viacheslav Kabanovich
>            Assignee: Viacheslav Kabanovich
>             Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> {code}
> java.lang.NullPointerException
> 	at org.jboss.tools.common.ui.JobResultFuture.cancel(JobResultFuture.java:49)
> 	at org.jboss.tools.common.ui.WizardUtils.waitForFuture(WizardUtils.java:157)
> 	at org.jboss.tools.common.ui.WizardUtils.access$0(WizardUtils.java:151)
> 	at org.jboss.tools.common.ui.WizardUtils$1.run(WizardUtils.java:139)
> 	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {code}
> For some time I could reproduce the exception in this steps:
> 1. Close Eclipse with OpenShift Explorer active and password for a connection unsaved. 
> 2. Open Eclipse - Sign In to OpenShift wizard appears.
> 3. Enter password and finish.
> 4. Progress appears but job does not start (I checked it in debugger) - ui jobs locked.
> 5. Only red button cancelling connection is active, press it - null pointer exception, ui is unlocked.
> 6. Start Sign In to OpenShift wizard with context menu - it can be completed successfully, connection is established.
> Later, after I received latest commits, the ui jobs lock could not be reproduced, so for now I do not report this usecase as a bug. But it is still possible to reproduce the same null pointer using breakpoints in debugger, because it happens if job is cancelled through JobResultFuture before job manager can start it.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)