[
https://issues.apache.org/jira/browse/ODE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678843#action_12678843
]
Ciaran Jessup commented on ODE-422:
-----------------------------------
We're only using in-memory processes (just be aware this patch doesn't touch
the hashcode function so that is still not 'safe', plus it doesn't test for
object reference equality) I had to re-apply it again to 1_x head to stop
various timeouts in my ode load tests :(
> 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.
