Skip to main content

[jsr352-public] Do we need another BatchStatus transition (mark jobs as FAILED)?

  • From: Scott Kurz < >
  • To:
  • Subject: [jsr352-public] Do we need another BatchStatus transition (mark jobs as FAILED)?
  • Date: Fri, 25 Oct 2013 22:47:46 -0400



I don't remember this issue being raised up until now (maybe it was in the
EG)...

Say a job is running along and someone kills the JVM or it hits OOM.
Can't the implementation determine somehow that jobs like this should be
moved into FAILED state (BatchStatus)?

I don't think the spec needs to specify how this happens... but it seems to
try to completely cover all state transitions, and it specifically
disallows restart of an already-STARTED job (in Sec. 10.8).

So I think it should say something allowing this "mark FAILED" transition
to occur in an impl-specific way.

Thoughts?
------------------------------------------------------
Scott Kurz
WebSphere Batch / Compute Grid Development
T/L 295-5649;
External Phone 845-435-5649

--------------------------------------------------------

[jsr352-public] Do we need another BatchStatus transition (mark jobs as FAILED)?

Scott Kurz 10/26/2013

[jsr352-public] Re: Do we need another BatchStatus transition (mark jobs as FAILED)?

Michael Minella 10/28/2013

[jsr352-public] Re: Do we need another BatchStatus transition (mark jobs as FAILED)?

Scott Kurz 10/28/2013

[jsr352-public] Re: Do we need another BatchStatus transition (mark jobs as FAILED)?

Michael Minella 10/28/2013

[jsr352-public] Re: Do we need another BatchStatus transition (mark jobs as FAILED)?

Scott Kurz 10/28/2013

[jsr352-public] Re: Do we need another BatchStatus transition (mark jobs as FAILED)?

Michael Minella 10/28/2013

[jsr352-public] Re: Do we need another BatchStatus transition (mark jobs as FAILED)?

Cheng Fang 10/28/2013
 
 
Close
loading
Please Confirm
Close