Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
Described just a bit more in:
https://github.com/WASdev/standards.jsr352.jbatch/issues/36
We're working on a TCK 1.1 test which will expose this issue.
Note that if you tried to recreate this today you'd probably hit a different symptom due to the bug fixed in my BATCHEE-54 patch in PartitionedStepController:
+ if (numTotalForThisExecution == 0) {
+ //All partitions have already completed on a previous execution
+ return;
The fix in:
https://github.com/WASdev/standards.jsr352.jbatch/commit/57fa84b23ea5ced5beed676edf5f634a97f08559
will likely help, though I don't have a JPA version yet.
I don't mind coming back to this, but I'll probably wait until the TCK test(s) are there to verify.