Spring Batch - retrieve exceptions with async job

Question

I'm configuring a (long running) job in Spring Batch with an async JobLauncher, and I have two REST endpoint:

/start --> will start the job asynchronously and return the job_execution_id to the client
/status/{job_execution_id} --> will return the status of the job execution based on data stored in JobExecutionContext

In the /status endpoint, I would like to inform the client about any exceptions occurred during the process. However, I'm not able to retrieve them in the way I was doing with the sync version of the same job:

   jobExecution.getAllFailureExceptions() --> empty list
   stepExecution.getFailureExceptions()  --> empty list

Is there a way to tell Spring Batch to store the exception stacktrace (or at least the exception message), so I can retrieve it later?

Thanks Giulio

Mahmoud Ben Hassine · Accepted Answer · 2021-06-08 21:21:49Z

1

Failure exceptions are added after the job execution is finished (more precisely right before the job is about to finish). So they are not available while the job is running. That's why you can't get them if you call the /status endpoint while the job is running asynchronously in the background.

The same applies for step failure exceptions, but those should be available as soon as the step is finished (while eventual subsequent steps are still running and the surrounding job as well).

answered Jun 8, 2021 at 21:21

Mahmoud Ben Hassine

32.1k5 gold badges38 silver badges67 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Giulio Pulina Over a year ago

Thanks for the answer, I completely understand your point about job failure exceptions. I was expecting, as you are saying, that step failure exceptions were stored in the database and could be retrieved via the JobExecution object, but it seems not to be the case: this works only in synchronous mode. I found a working solution using a StepExecutionListener (afterStep) to save the exception (if any) in the JobExecutionContext, so it will be serialized in the database and /status endpoint is able to access the exception: does it make sense to you?

Mahmoud Ben Hassine Over a year ago

I was expecting, as you are saying, that step failure exceptions were stored in the database and could be retrieved via the JobExecution object

: I did not say that, and I hope my answer did not imply that. Failure exceptions are transient and therefore they are not persisted in the database. They are only accessible through the in-memory StepExecution/JobExecution object after the step/job is finished.

Giulio Pulina Over a year ago

Thanks for the clarification and sorry for the misunderstanding, of course your answer didn't imply that the exceptions were stored in the database. In fact, also looking at the code, I came to the conclusion that I have to store the exception by myself, and, in fact, I'm already successfully doing it with a StepExecutionListener. Thanks again for the support.

Pascoal Eddy Bayonne · Accepted Answer · 2023-02-28 11:09:21Z

0

The same happens when you use Remote Chunking. There is no way that you can use the FaultTolerance with SkipPolicy, the manager configuration won't pick the listener.

For your particular case, very sad i had to use for example: StepExecutionListener and use the afterStep to get the exitDescription from ExitStatus. Well the best solution is using the Worker and handle there the exception.

answered Feb 28, 2023 at 11:09

Pascoal Eddy Bayonne

837 bronze badges

Collectives™ on Stack Overflow

Spring Batch - retrieve exceptions with async job

2 Answers 2

3 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related