This content has been marked as final.
Show 3 replies
-
1. Re: Restart job execution
xkylex May 22, 2015 6:42 AM (in response to lhelander)1 of 1 people found this helpfulIn newer JBeret (JBatch Runtime for WildFly), it introduced a new feature to address your problem, but I'm not sure it can run with WildFly 8.2.0.Final. for details see: https://issues.jboss.org/browse/JBERET-154
As to your observation that inconsistency of the batch status between the API and database, it looks like a bug. I've experienced it too with PostgreSQL repository.
-
2. Re: Restart job execution
xkylex May 22, 2015 8:40 AM (in response to xkylex)1 of 1 people found this helpfulI just found that the problem about inconsistency between the API and DB was fixed in here: JobOperatorImpl doesnt propagate status to repository · Issue #24 · jberet/jsr352 · GitHub
-
3. Re: Restart job execution
lhelander May 27, 2015 12:36 PM (in response to xkylex)Thank you very much for the clarification.