[jira] Commented: (ODE-422) NPE in Job.equals of scheduler

["Mark Ford (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ODE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677010#action_12677010 ] 

Mark Ford commented on ODE-422:
-------------------------------

I am getting this same issue with a parallel forEach that has four concurrent iterations with a simple assign / invoke / assign structure. The null job id comes from BpelRuntimeContextImpl.releasePartnerMex. The code there is looking for a property called "invokeCheckJobId" on the mexDAO which is not present.

The exception doesn't seem to have any negative side effects but it's disconcerting. I am running on the 1.x branch.

> NPE in Job.equals of scheduler
> ------------------------------
>
>                 Key: ODE-422
>                 URL: https://issues.apache.org/jira/browse/ODE-422
>             Project: ODE
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Windows Server 2003 SP2, Java 1.6.0-b105, Tomcat 5.5, ODE branch 1.2 revision 711434
>            Reporter: John Rossall
>            Priority: Minor
>             Fix For: 1.3
>
>         Attachments: Job.patch
>
>
> I get a null pointer exception in the equals method of org.apache.ode.scheduler.simple.Job. 
> This is because the job id is null. Why the job id is null i do not know, but the constructor allows a null job id.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.