[
https://issues.apache.org/jira/browse/SYSTEMML-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707219#comment-15707219
]
Felix Schüler commented on SYSTEMML-1131:
-----------------------------------------
A null-check around the whole synchronized block solves the problem - do you
think that"s the right way to go here? This will still create the new
instruction array.
Alternatively we could check every time if the recompile method is called with
a null hop and just skip the call.
> NPE in executeRemoteSparkParFor
> -------------------------------
>
> Key: SYSTEMML-1131
> URL: https://issues.apache.org/jira/browse/SYSTEMML-1131
> Project: SystemML
> Issue Type: Bug
> Reporter: Felix Schüler
>
> The method ParForProgramBlock.releaseForcedRecompile(long tid) calls
> recompileProgramBlockHierarchy2Forced with execution type (et) null. This
> leads to a NullPointerException.
> I haven't fully figured out under which circumstances this occurs but it
> happens when calling an external function inside a forced parfor_spark.
> The ParForProgramBlock.executeRemoteSparkParFor method sets the flagForced to
> true which then in turn calls the above method with et==null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
