[jsr352-public] Re: Questions about Exit status and restart
- From: Michael Minella <
- To: "
- Subject: [jsr352-public] Re: Questions about Exit status and restart
- Date: Tue, 12 Nov 2013 09:32:21 -0600
There is an open bug related to the behavior you are seeing:
As you note, the spec expects the ExitStatus to match the BatchStatus
unless set otherwise, yet the RI initializes it to null (due to what the
JavaDoc on the interface allows).
On Tue, Nov 12, 2013 at 9:24 AM,
> In the document, it says: "Exit status is initially set to the string
> form of the batch status." However, for my app, If my batch is failed,
> then both the step exit status and job exit status turn FAILED. If my
> batch is stopped, then the step exit status turns STOPPED, but the job
> exit status is null. Otherwise, both exit status are always null. Is
> this right?
> Second question, when the batch is failed, both exit status are
> FAILED(I only have one step in this job), I restart this jobexcution,
> the step cannot be restarted. Do I need some configuration in job.xml?
> Third question, could I force the job/step exit status to be always
> STOPPED? So that this batch could be restart even if it's completed.