In the 2.0.4 version, a new ItemReader would be instantiated each time my job was executed. In 2.1.0, the SAME ItemReader instance is being re-used (like a singleton).

This is a problem for me because the ItemReader has already exhausted its items and a flag has been set to return NULL.

I'm sure this is just a configuration issue. Unfortunately, I don't have time to track this down.

If anyone has an idea how to fix this , please let me know.

Thanks.