batchee-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (BATCHEE-112) MemoryPersistenceManagerService.jobOperatorGetRunningExecutions() throws NoSuchJobException
Date Wed, 07 Sep 2016 07:11:20 GMT

     [ https://issues.apache.org/jira/browse/BATCHEE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Romain Manni-Bucau resolved BATCHEE-112.
----------------------------------------
    Resolution: Fixed

> MemoryPersistenceManagerService.jobOperatorGetRunningExecutions() throws NoSuchJobException
> -------------------------------------------------------------------------------------------
>
>                 Key: BATCHEE-112
>                 URL: https://issues.apache.org/jira/browse/BATCHEE-112
>             Project: BatchEE
>          Issue Type: Bug
>          Components: jbatch-core
>            Reporter: Scott Kurz
>            Assignee: Reinhard Sandtner
>            Priority: Minor
>
> As reported here:
> http://stackoverflow.com/questions/39013258/batchee-getrunningexecutions-method-throws-javax-batch-operations-nosuchjobexcep
> I took a quick look and the JPA persistence looks fine.. but the in-memory one seems
to have a bug (which presumably the SO user was using). The code breaks out of the loop as
soon as it finds an instance matching the job name.   But really every job instance should
be looked at, not just the first one. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message