db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2751) testLoadJavaClassIndirectly & als fails on JVM 1.4 with "Unexpected SQL state. expected:<[38000]> but was:<[XJ001]>", "Jar file 'MY_JAVA' already exists in Schema 'EMC'"
Date Mon, 04 Jun 2007 15:32:36 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501244
] 

Knut Anders Hatlen commented on DERBY-2751:
-------------------------------------------

This happens because the class files in java/testing/org/apache/derbyTesting/functionTests/tests/lang/dcl_java.jar
are compiled with 1.5. Wouldn't it be better if the java files were checked in as normal source
files in Subversion and the build scripts created the jar file?

> testLoadJavaClassIndirectly & als fails on JVM 1.4 with "Unexpected SQL state. expected:<[38000]>
but was:<[XJ001]>", "Jar file 'MY_JAVA' already exists in Schema 'EMC'"
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2751
>                 URL: https://issues.apache.org/jira/browse/DERBY-2751
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.3.0.0
>         Environment: OS: All ?
> JVM: Sun Microsystems Inc. 1.4.2_02-b03, Sun Microsystems Inc. 1.4.2_13-b06, 
>            Reporter: Ole Solberg
>            Priority: Minor
>
> 1) testLoadJavaClassDirectly(org.apache.derbyTesting.functionTests.tests.lang.DatabaseClassLoadingTest)java.sql.SQLException:
Jar file 'MY_JAVA' already exists in Schema 'EMC'.
> 2) testLoadJavaClassDirectly2(org.apache.derbyTesting.functionTests.tests.lang.DatabaseClassLoadingTest)java.sql.SQLException:
Jar file 'MY_JAVA' already exists in Schema 'EMC'.
> 3) testLoadJavaClassDirectly3(org.apache.derbyTesting.functionTests.tests.lang.DatabaseClassLoadingTest)java.sql.SQLException:
Jar file 'MY_JAVA' already exists in Schema 'EMC'.
> 4) testLoadDerbyClassIndirectly(org.apache.derbyTesting.functionTests.tests.lang.DatabaseClassLoadingTest)java.sql.SQLException:
Jar file 'MY_JAVA' already exists in Schema 'EMC'.
> 1) testLoadJavaClassIndirectly(org.apache.derbyTesting.functionTests.tests.lang.DatabaseClassLoadingTest)junit.framework.ComparisonFailure:
Unexpected SQL state. expected:<[38000]> but was:<[XJ001]>
> See e.g.
> http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-543922.html
> http://dbtg.thresher.com/derby/test/trunk16/jvmAll/testing/Limited/testSummary-543945.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message