[
https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-3427:
--------------------------------------
Attachment: d3427.diff
Attached is a patch (d3427.diff) which fixes the bug by using the prepareCall()
method with a holdability parameter in DRDAStatement. The patch also removes
DRDAStatement.prepareStatementJDBC3() since we can now use
Connection.prepareStatement(String,int,int,int) directly.
(prepareStatementJDBC3() additionally contains some logic to handle the case
where the holdability is uninitialized, but at this point in the code we know
that the holdability is initialized because of the call to
parsePkgidToFindHoldability().)
A test case has been added to BlobClob4BlobTest. It fails without the fix in
DRDAStatement and succeeds with the fix.
I saw these errors when running the regression tests:
- predicatePushdown (DERBY-3479)
- st_reclaim_longcol (DERBY-1913)
- TransactionTable (also seen in the nightly tests)
- ManagementMBeanTest (also seen in the nightly tests)
> setting transaction isolation level to read committed raise ERROR X0X03:
> Invalid transaction state - held cursor requires same isolation level
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3427
> URL: https://issues.apache.org/jira/browse/DERBY-3427
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.3.1.4, 10.3.2.1
> Environment: windows XP Java version 1.6.0_03
> Reporter: Rene Levantinh
> Assignee: Knut Anders Hatlen
> Priority: Critical
> Attachments: d3427.diff, SimpleNetworkClientSample1.java,
> SimpleNetworkServerSample.java, use-holdability.diff
>
>
> setting transaction isolation level to read committed after reading a BLOG
> record raise ERROR X0X03: Invalid transaction state - held cursor requires
> same isolation level .
> Using Derby client 10.2 either with Derby server 10.3 or 10.2 works
> fine .
> Using Derby Client 10.3 with Derby Server 10.2 also work fine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
