db-derby-dev mailing list archives

[jira] Reopened: (DERBY-366) In jdk13, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored.

Date

Tue, 11 Apr 2006 18:17:21 GMT

[ http://issues.apache.org/jira/browse/DERBY-366?page=all ]
Mamta A. Satoor reopened DERBY-366:
-----------------------------------
Need to mark correct fixin version for this Jira entry
> In jdk13, when a connection transitions from global transaction to local transaction,
its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-366
> URL: http://issues.apache.org/jira/browse/DERBY-366
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.0.2.1
> Reporter: Mamta A. Satoor
> Assignee: Mamta A. Satoor
> Attachments: Derby8_Derby366_061805.txt, mamta.java
>
> A connection in local transaction has a default holdability of HOLD_CURSORS_OVER_COMMIT.
When this connection becomes part of a global transaction, Derby internally switches its holdability
to CLOSE_CURSORS_AT_COMMIT (this is because in Derby, holdable cursors do not work with XA
transactions). When this connection returns back to local transaction, its holdability should
automatically get switched to HOLD_CURSORS_OVER_COMMIT. When running under jdk13, Derby does
not perform the last step of restoring the connection holdability. I have attached a program
to reporduce this behavior. If this program is run under jdk14, the holdability is restored
as expected.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira