[
https://issues.apache.org/jira/browse/DERBY-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-1370:
----------------------------------
Description:
See this thread: http://www.nabble.com/XA-and-holdability-p4671213.html
It looks like embedded behaviour is correct and client has to match this. This
has to be confirmed though.
was:
See this thread: http://www.nabble.com/XA-and-holdability-p4671213.html
It looks like embedded behaviour is correct and client has to match this. This
has to be confirmed though.
Issue & fix info: [High Value Fix, Repro attached]
Urgency: Low
Labels: derby_triage10_8 (was: )
Triage for 10.8.
In the thread Deepa said she encountered this when converting checkDataSource30
test which I think was converted to J2EEDataSourceTest. There are comments
about DERBY-1370 in that test but they don't quite seem to match up to the
description of this bug. I don't think a global transaction can have holdable
transaction under any circumstances.
> Embedded and client driver differ in the holdability reported inside a global
> transaction for statements that were created with HOLD_CURSORS_OVER_COMMIT
> outside the transaction
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1370
> URL: https://issues.apache.org/jira/browse/DERBY-1370
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.1.3.1, 10.2.1.6
> Reporter: Deepa Remesh
> Priority: Minor
> Labels: derby_triage10_8
>
> See this thread: http://www.nabble.com/XA-and-holdability-p4671213.html
> It looks like embedded behaviour is correct and client has to match this.
> This has to be confirmed though.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
