Oct 15th, 2012, 01:08 AM
Job is not going to failed state even when the Item Reader is throwing an exception.
Job is getting set as COMPLETED even when the CustomItemReader has thrown and "UnexpectedInputException" is thrown.
Is this the expected behavior??
I would also like to know under what conditions a job will be get set to FAILED state?
Oct 22nd, 2012, 04:54 PM
Without seeing the code, I can't be sure. If an ItemReader throws an exception that is not retried or skipped, however, the framework should mark the step failed.