You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Ole Solberg (JIRA)" <ji...@apache.org> on 2007/06/06 15:36:25 UTC
[jira] Created: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
--------------------------------------------------------------------------------------------------------------------------
Key: DERBY-2770
URL: https://issues.apache.org/jira/browse/DERBY-2770
Project: Derby
Issue Type: Bug
Components: JDBC
Affects Versions: 10.3.0.0
Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
JVM: Sun Microsystems Inc. 1.6.0_01-b06
Reporter: Ole Solberg
Priority: Minor
testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
after
r544777 / DERBY-2729
See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Øystein Grøvlen reassigned DERBY-2770:
--------------------------------------
Assignee: Øystein Grøvlen (was: Kristian Waagan)
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Øystein Grøvlen
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, derby-2770-2a.diff, derby-2770-2a.stat, derby-2770-2b.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-2770:
-----------------------------------
Attachment: derby-2770-1a.diff
'derby-2770-1a.diff' changes the BlobClob4Blob test to not fail. The test failed because the SQL state was changed, possibly the location where the error checking is done changed.
As part of looking into this issue I discovered that the client reports another SQLState when accessing Blobs after commit, see DERBY-2771.
I request a review from someone familiar with Blob and locators in the client for this patch.
After applying the patch, BlobClob4Blob runs without failures.
As the changes is in the test only and basically localized to one test method, I'm committing the preliminary patch now to stop the tests from failing. It can easily be reverted, and I believe the test has to change anyway if/when DERBY-2771 is addressed.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Priority: Minor
> Attachments: derby-2770-1a.diff
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502304 ]
Øystein Grøvlen commented on DERBY-2770:
----------------------------------------
Thanks, Anurag, that explains it.
So the correct fix is not to assert on XJ217, but on XJ073.
Or better, change XJ073 to match the error code used for embedded.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502278 ]
Knut Anders Hatlen commented on DERBY-2770:
-------------------------------------------
Just guessing here, but I noticed this:
- both BLOBCREATELOCATOR and CLOBCREATELOCATOR call addLOBMapping
- EmbedBlob's constructors call addLOBMapping, but EmbedClob's constructors don't
- Narayanan's test uses createBlob()/createClob(), hence addLOBMapping is always called
- testBlobAfterCommit() and testClobAfterCommit() get the lobs from ResultSet.get[BC]lob(), hence addLOBMapping is only called for the BLOB test
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503410 ]
Øystein Grøvlen commented on DERBY-2770:
----------------------------------------
I will address the inconsistent comments when DERBY-2787 has been committed since that check-in will change things for Clob.
With respect to the error message, I just copied the phrase from the error message previously used. If most people think, Knut Anders' suggestion is better, I will change it.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Øystein Grøvlen
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, derby-2770-2a.diff, derby-2770-2a.stat, derby-2770-2b.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
V.Narayanan updated DERBY-2770:
-------------------------------
Attachment: ExceptionTest.java
I used the above test program. I wrote it in a hurry.
Pls forgive any silly mistakes you see.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL
state. expected: but was:'
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
"Knut Anders Hatlen (JIRA)" <ji...@apache.org> writes:
> From: "Knut Anders Hatlen (JIRA)" <ji...@apache.org>
> Subject: [jira] Commented: (DERBY-2770)
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL
> state. expected:<XJ[073]> but was:<XJ[215]>'
> To: derby-dev@db.apache.org
> Date: Thu, 07 Jun 2007 05:12:26 -0700 (PDT)
> Reply-to: derby-dev@db.apache.org
>
>
> [ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502316 ]
>
> Knut Anders Hatlen commented on DERBY-2770:
> -------------------------------------------
>
> Sorry, my last comment was wrong. assertSQLState() *does* traverse the entire chain.
Haha, I fell into the same trap, did not expect to see used recursion
here. Still, the question remains whether this could mask
wrong/unexpected behavior..
Dag
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502316 ]
Knut Anders Hatlen commented on DERBY-2770:
-------------------------------------------
Sorry, my last comment was wrong. assertSQLState() *does* traverse the entire chain.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Øystein Grøvlen updated DERBY-2770:
-----------------------------------
Derby Info: [Patch Available, Regression] (was: [Regression])
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, derby-2770-2a.diff, derby-2770-2a.stat, derby-2770-2b.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Ole Solberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Solberg closed DERBY-2770.
------------------------------
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Øystein Grøvlen
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, derby-2770-2a.diff, derby-2770-2a.stat, derby-2770-2b.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
V.Narayanan updated DERBY-2770:
-------------------------------
Attachment: derby-2770-2a.stat
derby-2770-2a.diff
I changed the test to check for BLOB_ACCESSED_AFTER_COMMIT.
It seems to work fine.
I think this explains that the SQLState returned by client remains
unaffected
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, derby-2770-2a.diff, derby-2770-2a.stat, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Øystein Grøvlen resolved DERBY-2770.
------------------------------------
Resolution: Fixed
DERBY-2787 cleans up the inconsistent comments that Knut Anders reported.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Øystein Grøvlen
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, derby-2770-2a.diff, derby-2770-2a.stat, derby-2770-2b.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502281 ]
Øystein Grøvlen commented on DERBY-2770:
----------------------------------------
This problem is caused by the check-in of DERBY-2729, and Anurag says in that report that it only changes things for Blob, and that a Clob patch will come later. I think that answer's Narayanan question about why the error only happens for Blob.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Øystein Grøvlen updated DERBY-2770:
-----------------------------------
Attachment: derby-2770-2b.diff
Attached file, derby-2770-2b.diff, changes the client to used the same
SQL state as embedded for Blobs accessed after transaction has
committed. Since Clob has yet to get the new behavior, there will now
be a difference between client and embedded for Clobs. However, I
expect that to be fixed by Anurag when it posts his corresponding
patch for Blob.
The following files are changed by this patch:
M java/engine/org/apache/derby/loc/messages.xml
Changed error message to reflect that XJ215 is used both after
free() has been called on a Lob and after the lob's transaction has
been committed.
M java/client/org/apache/derby/client/am/CallableLocatorProcedures.java
Change SQL state to use when locators are invalid from XJ073 to
XJ215. Also, Knut Anders has since this method was created, made
nested exceptions with SQL state available on the client. Hence,
we can now check for SQL state directly instead resorting to text
search of error messages.
M java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/BlobClob4BlobTest.java
Change tests to except the changed SQL state for access after
commit.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, derby-2770-2a.diff, derby-2770-2a.stat, derby-2770-2b.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL
state. expected: but was:'
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
"Knut Anders Hatlen (JIRA)" <ji...@apache.org> writes:
> assertSQLState() succeeds if the main SQLException or its next
> exception matches. It doesn't traverse the entire chain.
Why two levels only? And is this always advisable? Seems to be it
could mask wrong behavior. The comment in the code seems to indicate
the intention is to check all, though ("any of them"...)
:
// Check nested exceptions to see if any of them is
// the one we're looking for.
exception = exception.getNextException();
if (exception != null)
assertSQLState(message, expected, exception);
else
throw e;
Dag
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502313 ]
Knut Anders Hatlen commented on DERBY-2770:
-------------------------------------------
assertSQLState() succeeds if the main SQLException or its next exception matches. It doesn't traverse the entire chain.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502310 ]
Øystein Grøvlen commented on DERBY-2770:
----------------------------------------
Maybe not, I think I am still confused. The test used to test for XJ073, but that evidently did not work.
As far as I can see assertException will be satisfied as long as at least one of the states in the exception chain matches.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502707 ]
Øystein Grøvlen commented on DERBY-2770:
----------------------------------------
Junit All suite and derbyall ran without errors (except the upgrade test which I have not set up correctly).
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, derby-2770-2a.diff, derby-2770-2a.stat, derby-2770-2b.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Anurag Shekhar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502301 ]
Anurag Shekhar commented on DERBY-2770:
---------------------------------------
assertException checks for SQLState in nested exception. One of the exception received using getNextException has sql state set to XJ217.
I added following code to catch block of Narayanan's code
while (sqle != null) {
System.out.println("THE EXCEPTION SQLSTATE IS =" + sqle.getSQLState());
sqle = sqle.getNextException();
}
It outputs
THE EXCEPTION SQLSTATE IS =XJ073
THE EXCEPTION SQLSTATE IS =38000
THE EXCEPTION SQLSTATE IS =XJ217
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502234 ]
V.Narayanan commented on DERBY-2770:
------------------------------------
Thank you for looking into this and fixing the tests
I am a little worried about this, more so probably because I get
contrasting results with a small test program I wrote
Should'nt the following series of tests produce the same result of this test?
1) Get a connection to the network server (con)
2) Get a empty Clob or Blob (con.createClob() or con.createBlob())
3) do a con.commit()
4) call length on the Clob or Blob(clob.length() or blob.length())
I get the same SQLState for the exception in both
the cases with an SQLState of XJ073. Maybe I missed something
while writing the program because I wrote the program in a hurry.
Why is testClobAfterCommit() not failing? Locators have been enabled
for Clob too why hasn't it failed.
I am surely missing something really simple I think.
I will attach the test program also, so that in case I have made some
mistake there you can point it out.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502284 ]
V.Narayanan commented on DERBY-2770:
------------------------------------
Yes, I tried this too, I agree I saw similar behaviour. Does this have
anything to do with the size of the Blob fetched or
whether it is materialized or not ?
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-2770:
-----------------------------------
Fix Version/s: 10.3.0.0
Assignee: Kristian Waagan
Committed 1a to trunk with revision 544856.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502283 ]
Kristian Waagan commented on DERBY-2770:
----------------------------------------
I modified Narayanans test program to fetch the Blob from a resultset. It still works correctly and provokes the XJ073 error.
However, the BlobClob4Blob test do still run without failures when expecting XJ217.
Maybe we could have a look at the stack traces for the two cases?
Is the test doing something in a special manner?
I would also use this opportunity to suggest that in near future the BlobClob4Blob test should be rewritten or split into several test classes. It is ~3200 lines long... That said, I think it has lots of good tests!
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-2770:
--------------------------------------
Derby Info: [Regression] (was: [Regression, Patch Available])
Committed derby-2770-2b.diff with revision 545910.
I noticed that there are many comments in BlobClob4BlobTest that say
//The same SQLState String BLOB_ACCESSED_AFTER_COMMIT
//is used for LOB's(Both Clob and Blob). Ensure that
//we get the expected exception by comparing the SQLState.
These comments should be updated to reflect the changed SQL state.
The new error message uses the term "the Blob/Clob's transaction". Would it be clearer to say "the transaction in which the Blob/Clob was created"?
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Øystein Grøvlen
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, derby-2770-2a.diff, derby-2770-2a.stat, derby-2770-2b.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2770)
testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected
SQL state. expected: but was:'
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502315 ]
Øystein Grøvlen commented on DERBY-2770:
----------------------------------------
If you look at the original problem reported by Ole, it was just tests of embedded that failed.
The changes to the test for client/server does not seem to be necessary. It happens that the exception chaing (as pointed out by Anurag) contains both XJ073 and XJ217 so testing for any of them would work.
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.