Issue Details (XML | Word | Printable)

Key: DERBY-22
Type: Bug Bug
Status: Resolved Resolved
Resolution: Cannot Reproduce
Priority: Minor Minor
Assignee: Unassigned
Reporter: Tulika Agrawal
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Derby

Exception XCL16 incorrectly raised for ResultSet of method return after nested commit.

Created: 29/Sep/04 07:15 PM   Updated: 15/Oct/07 07:44 PM
Return to search
Component/s: SQL
Affects Version/s: 10.0.2.0
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments:
  Size
Zip Archive Licensed for inclusion in ASF works derby22reproattempt.zip 2007-07-31 04:57 PM Kathey Marsden 1 kB
Zip Archive Licensed for inclusion in ASF works derby22reproattempt.zip 2007-07-30 09:32 PM Kathey Marsden 1 kB

Resolution Date: 15/Oct/07 07:44 PM


 Description  « Hide
Reporting for Daniel John Debrunner.

A static method calls commit() with the nested connection and
then returns a value to the outer statement. Processing this
result set incorrectly hits a XCL16 exception. Logically the
result set is created after the commit, since the value is
returned after the commit.


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Shreyas Kaushik added a comment - 03/Feb/05 09:28 PM
Can there be a repro posted for this here?

Kathey Marsden added a comment - 30/Jul/07 09:32 PM
Attached is an attempted repro of this issue based on the description, but it doesn't seem to fail. Perhaps it has been already fixed or perhaps I errored in trying to reproduce the issue. Dan could you comment on which might be the case.

Thanks

Kathey

Daniel John Debrunner added a comment - 31/Jul/07 04:38 PM
Try with the connection in close cursors on commit mode.

Kathey Marsden added a comment - 31/Jul/07 04:57 PM
Here is another attempt to reproduce, setting the connection to CLOSE_CURSORS_AT_COMMIT, but still cannot reproduce. Ideas?



Kathey Marsden added a comment - 15/Oct/07 07:44 PM
Was not able to reproduce this error. The issue can be reopened if we get a repro.

Kathey