[jira] Updated: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
[ https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3427: -- Component/s: SQL > 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 > Components: SQL >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 > Fix For: 10.3.3.0, 10.4.1.3 > > 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.
[jira] Updated: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
[ https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3427: -- Fix Version/s: 10.3.2.2 I'm adding 10.3.2.2 to the list of fix versions as I think this is a good candidate for merging to 10.3 > 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 > Fix For: 10.3.2.2, 10.4.0.0 > > 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.
[jira] Updated: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
[ https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3427: -- Derby Info: [Regression] (was: [Regression, Patch Available]) Fix Version/s: 10.4.0.0 Thanks for reviewing the patch, Dyre. Committed revision 634206. > 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 > Fix For: 10.4.0.0 > > 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.
[jira] Updated: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
[ https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3427: -- Derby Info: [Patch Available, Regression] (was: [Regression]) > 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.
[jira] Updated: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
[ 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.
[jira] Updated: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
[ https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3427: -- Attachment: use-holdability.diff Here's an alternative (and untested) approach. I changed the network server so that it used the specified holdability instead of the default holdability when preparing calls. It seems to fix the repro. > 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 >Priority: Critical > Attachments: 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.
[jira] Updated: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
[ https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3427: -- Derby Info: [Regression] > 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 >Priority: Critical > Attachments: SimpleNetworkClientSample1.java, > SimpleNetworkServerSample.java > > > 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.
[jira] Updated: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
[ https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3427: -- Comment: was deleted > 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 >Priority: Critical > Attachments: SimpleNetworkClientSample1.java, > SimpleNetworkServerSample.java > > > 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.
[jira] Updated: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
[ https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rene Levantinh updated DERBY-3427: -- Attachment: SimpleNetworkServerSample.java SimpleNetworkClientSample1.java The server part is the demo found in the distribution file. The client part is a modified version found in the distribution file to reproduce the bug. > 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 >Priority: Critical > Attachments: SimpleNetworkClientSample1.java, > SimpleNetworkServerSample.java > > > 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.
