[
https://issues.apache.org/jira/browse/DERBY-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-6760:
--------------------------------------
Attachment: DERBY-6610_1.diff
It appears the ibm 1.6 jvm is wrapping the SQLException in a StandardException
and it is throwing an SQLException with SQLState 38000.
I am attaching a patch which will accept a 38000 for this JVM.
I'll commit this shortly.
If there's a more elegant way of checking whether there's a reference to
'XIE0S' somewhere in the stack trace we can adjust the test later.
> test_01_planCost has been failing for last couple nights on trunk and 10.11
> with Unexpected SQL state. expected:<XIE0S> but was:<null>
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6760
> URL: https://issues.apache.org/jira/browse/DERBY-6760
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.11.1.3, 10.12.0.0
> Reporter: Mamta A. Satoor
> Assignee: Myrna van Lunteren
> Attachments: DERBY-6610_1.diff
>
>
> test_01_planCost has failed on trunk and 10.11 for last couple nightly runs.
> Output from 10.11(revision 1629345) test run is as follows
> http://people.apache.org/~myrnavl/derby_test_results/v10_11/linux/testlog/ibm16/1629345-suites.All_diff.txt
> 1)
> test_01_planCost(org.apache.derbyTesting.functionTests.tests.lang.XMLOptimizerTraceTest)junit.framework.ComparisonFailure:
> Unexpected SQL state. expected:<XIE0S> but was:<null>
> Caused by: java.sql.SQLException: java.sql.SQLException: The operation was
> not performed, because the specified output file (extinout/xott.xml) already
> exists. The procedure will not overwrite an existing file, even if the
> process has permissions to write to that file, due to security concerns, and
> to avoid accidental file damage. Please either change the output file name in
> the procedure arguments to specify a file which does not exist, or delete the
> existing file, then retry the operation.
> Caused by: java.security.PrivilegedActionException: java.sql.SQLException:
> The operation was not performed, because the specified output file
> (extinout/xott.xml) already exists. The procedure will not overwrite an
> existing file, even if the process has permissions to write to that file, due
> to security concerns, and to avoid accidental file damage. Please either
> change the output file name in the procedure arguments to specify a file
> which does not exist, or delete the existing file, then retry the operation.
> Caused by: java.sql.SQLException: The operation was not performed, because
> the specified output file (extinout/xott.xml) already exists. The procedure
> will not overwrite an existing file, even if the process has permissions to
> write to that file, due to security concerns, and to avoid accidental file
> damage. Please either change the output file name in the procedure arguments
> to specify a file which does not exist, or delete the existing file, then
> retry the operation.
> Caused by: ERROR XIE0S: The operation was not performed, because the
> specified output file (extinout/xott.xml) already exists. The procedure will
> not overwrite an existing file, even if the process has permissions to write
> to that file, due to security concerns, and to avoid accidental file damage.
> Please either change the output file name in the procedure arguments to
> specify a file which does not exist, or delete the existing file, then retry
> the operation.
> 2)
> test_01_planCost(org.apache.derbyTesting.functionTests.tests.lang.XMLOptimizerTraceTest)junit.framework.AssertionFailedError:
> The exception's SQL state must be five characters long
> Caused by: java.sql.SQLNonTransientConnectionException:
> java.sql.SQLException: The operation was not performed, because the specified
> output file (extinout/xott.xml) already exists. The procedure will not
> overwrite an existing file, even if the process has permissions to write to
> that file, due to security concerns, and to avoid accidental file damage.
> Please either change the output file name in the procedure arguments to
> specify a file which does not exist, or delete the existing file, then retry
> the operation.
> Caused by: ERROR null: java.sql.SQLException: The operation was not
> performed, because the specified output file (extinout/xott.xml) already
> exists. The procedure will not overwrite an existing file, even if the
> process has permissions to write to that file, due to security concerns, and
> to avoid accidental file damage. Please either change the output file name in
> the procedure arguments to specify a file which does not exist, or delete the
> existing file, then retry the operation.
> The failures from trunk are at
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1629352-suites.All_diff.txt
> http://people.apache.org/~myrnavl/derby_test_results/main/linux/testlog/ibm16/1629345-suites.All_diff.txt
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
