Problem with ITEM_COUNT and COMMIT_COUNT

I think this could be captured as a gotcha in the User guide(not to consume the exception, but to let the Batch FW to know this has happened)

Hey Dave.

Thanx for explaining the ITEM_COUNT values.

My skip limit is set to 2. There was a mistake in the xml I posted. I am not sure how to find out rollback count. So now you can put some light on COMMIT_COUNT = 3.

Also please indicated how to use ITEM_COUNT. Our monitoring team is looking at the ITEM_COUNT as how many records are processed successfully.
Which I think not correct meaning of ITEM_COUNT according to you.

ITEM_COUNT will show you how many records are read? Is there any way to find out how many records are processed successfully at perticular instance during the job execution? We require this for some estimates like how much percentage is complete and how much is remaining. I though ITEM_COUNT will be helpful in some way however looking at the way it is getting updated is not what we expect.

Please tell us the way if there is any.

If you are not expecting any failures then item count is fine. I guess if there are failures you have to subtract the rollback count times the commit interval and the skip count to get the number of items processed successfully. Or you could count them yourself in the writer and store them in the execution context, or in your own separate table.

Sorry for the hassle. We might be able to make some changes in 2.0 to make the counting reflect more what you expect. There is also a possibility that we might explicitly support percentage complete estimation.