Results 1 to 2 of 2

Thread: ItemReader instance re-used ? Issue upgrading to 2.1.0 from 2.0.4

  1. Feb 23rd, 2010, 10:17 AM #1
    sometxdude
    sometxdude is offline Member
    Join Date
    Jul 2006
    Location
    Houston, TX
    Posts
    80

    Question ItemReader instance re-used ? Issue upgrading to 2.1.0 from 2.0.4

    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.
    Reply With Quote Reply With Quote
  2. Feb 26th, 2010, 07:49 AM #2
    Dave Syer
    Dave Syer is offline Senior Member
    Join Date
    Jun 2005
    Posts
    4,230

    Default

    Not much to go on here, so you'll have to provide a bit more information if you want anyone else to spend their (equally valuable) time on your problem. Some configuration maybe?
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules