[
https://issues.jboss.org/browse/TEIID-2395?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2395.
-----------------------------------
Resolution: Rejected
The patch must be applied incorrectly. When I run the test case I see:
TimerExecution.TimerExecution()
TimerExecution.execute() RESULT
TimerExecution.close()
On Row 2013-02-15 08:12:37.3
TimerExecution.reset()
TimerExecution.execute() WAIT
TimerExecution.execute() RESULT
TimerExecution.close()
On Row 2013-02-15 08:12:37.603
TimerExecution.reset()
TimerExecution.execute() WAIT
TimerExecution.execute() RESULT
TimerExecution.close()
On Row 2013-02-15 08:12:37.705
TimerExecution.reset()
TimerExecution.execute() WAIT
TimerExecution.execute() RESULT
TimerExecution.close()
...
In general with something like this you'll need to reproduce the issue against the
current version (even if it's a prerelease) rather than against a patched version
before logging an issue.
ReusableExecutions are created everytime after DataNotAvailable is
thrown
-------------------------------------------------------------------------
Key: TEIID-2395
URL:
https://issues.jboss.org/browse/TEIID-2395
Project: Teiid
Issue Type: Bug
Affects Versions: 8.1
Reporter: Sanjeev Gour
Assignee: Steven Hawkins
Attachments: Testcase.zip
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira