[ 
http://issues.apache.org/jira/browse/DERBY-1005?page=comments#action_12420697 ] 

Deepa Remesh commented on DERBY-1005:
-------------------------------------

This issue was not fixed in 10.1.2.3. There was one more patch for this issue 
which went in later (svn revision# 412258). Currently there is no way to edit 
the issue and remove 10.1.2.3 from fix version as it is an archived fix 
version. Hence adding this comment. 

The fix is available in 10.1.3.


> getHoldability does not return CLOSE_CURSORS_AT_COMMIT in a global transaction
> ------------------------------------------------------------------------------
>
>          Key: DERBY-1005
>          URL: http://issues.apache.org/jira/browse/DERBY-1005
>      Project: Derby
>         Type: Bug

>   Components: Network Client
>     Versions: 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.1.2.3
>     Reporter: Kathey Marsden
>     Assignee: Daniel John Debrunner
>      Fix For: 10.2.0.0, 10.1.3.0, 10.1.2.3

>
> Holdability for a connection should automatically become 
> CLOSE_CURSORS_AT_COMMIT for a global transaction.
> For client xa Connection.getHoldability returns OLD_CURSORS_OVER_COMMIT 
> within a global transaction.
> This issue was discovered when converting checkDataSource30.java to run with 
> client and related code was disabled for client testing.
> To reproduce,  take out if (TestUtil.isEmbeddedFramework())   for this code 
> in jdbcapi/checkDataSource30.java
> if (TestUtil.isEmbeddedFramework())
>                       {
>                               // run only for embedded
>                               // Network XA BUG: getHoldability does not 
> return CLOSE_CURSORS_AT_COMMIT for global transaction
>                               System.out.println("Notice that connection's 
> holdability at this point is CLOSE_CURSORS_AT_COMMIT because it is part of 
> the global transaction");
>                               System.out.println("CONNECTION(in xa 
> transaction) HOLDABILITY " + (conn1.getHoldability() == 
> ResultSet.HOLD_CURSORS_OVER_COMMIT));
>                       }

-- 
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

Reply via email to