We're seeing many partitioned steps failing with an "EXIT_MESSAGE" of JobInterruptedException.

There are definitely exceptions coming from readers, processors and writers for a whole host of reasons but I do not understand why they would lead to Spring Batch then stopping the step with a JobInterruptedException.

Before I start uploading lots of code and xml I'd like to get a better understanding of the philosophy behind the JobInterruptedException, what it represents and the states that makes it occur.

With that information I may be able to more easily track down the root cause myself.

If anyone has any useful insights they would be much appreciated.

Thanks,
Jon