ReusableExecutions are created everytime after DataNotAvailable is thrown

We did a test with a simple ReusableExecution and found that new executions are being created every time after DataNotAvailableExecption is thrown. Here is the life cycle after the recent patch for issue https://issues.jboss.org/browse/TEIID-2322 was applied-

TimerExecution.TimerExecution()
TimerExecution.execute() RESULT
TimerExecution.close()
On Row 2013-02-15 17:41:03.421
TimerExecution.reset()
TimerExecution.execute() WAIT
TimerExecution.TimerExecution()
TimerExecution.execute() RESULT
TimerExecution.close()

On Row 2013-02-15 17:41:03.556

TimerExecution.reset()
TimerExecution.execute() WAIT
TimerExecution.TimerExecution()
TimerExecution.execute() RESULT
TimerExecution.close()
On Row 2013-02-15 17:41:03.661
TimerExecution.reset()
TimerExecution.execute() WAIT
TimerExecution.TimerExecution()
TimerExecution.execute() RESULT
TimerExecution.close()
On Row 2013-02-15 17:41:03.766
TimerExecution.reset()
TimerExecution.execute() WAIT

The same test when run against the jar before the fix was applied is this-

TimerExecution.TimerExecution()
TimerExecution.execute() RESULT
TimerExecution.close()
On Row 2013-02-15 17:49:01.998
TimerExecution.reset()
TimerExecution.execute() WAIT
TimerExecution.reset()
TimerExecution.execute() RESULT
TimerExecution.close()
On Row 2013-02-15 17:49:02.123
TimerExecution.reset()
TimerExecution.execute() WAIT
TimerExecution.reset()
TimerExecution.execute() RESULT
TimerExecution.close()
On Row 2013-02-15 17:49:02.228
TimerExecution.reset()
TimerExecution.execute() WAIT
TimerExecution.reset()
TimerExecution.execute() RESULT
TimerExecution.close()
On Row 2013-02-15 17:49:02.333
TimerExecution.reset()
TimerExecution.execute() WAIT
TimerExecution.reset()
TimerExecution.execute() RESULT
TimerExecution.close()
On Row 2013-02-15 17:49:02.438
TimerExecution.reset()
TimerExecution.execute() WAIT
TimerExecution.reset()

The testcase is attached.