Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <257104577.1239786735276.JavaMail.jira@brutus>
Date: Wed, 15 Apr 2009 02:12:15 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4133) 'testTableFunctionInJar' fails w/
 'The class 'DummyVTI' does not exist or is inaccessible...' on jvm1.4
In-Reply-To: <1623627546.1238494671098.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699127#action_12699127 ] 

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

I don't see anything in dummy_vti.jar that requires Java 5. Couldn't we just rebuild that jar file with a 1.4 compiler so that it gets tested on 1.4 too and we don't need to clutter the test with version checks?

Also, if we disable a test, I think we should do that in the suite() method and not from inside the test case. The way it is disabled now, JUnit will report that the test case passed on Java 1.4, whereas it in fact didn't run.

> 'testTableFunctionInJar' fails w/ 'The class 'DummyVTI' does not exist or is inaccessible...' on jvm1.4
> -------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4133
>                 URL: https://issues.apache.org/jira/browse/DERBY-4133
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.6.0.0
>         Environment: OS: All?
> JVM:
> Sun Microsystems Inc.
> java version "1.4.2_02"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_02-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_02-b03 mixed mode 32-bit)
>            Reporter: Ole Solberg
>            Assignee: Rick Hillegas
>            Priority: Minor
>         Attachments: derby-4133-01-aa-disableOn1.4.diff
>
>
> Seen in tests on jvm1.4 since ~ svn rev. 759509
> See e.g.
> http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-759509.html
> E.g.:
> 1) testTableFunctionInJar(org.apache.derbyTesting.functionTests.tests.lang.DatabaseClassLoadingTest)java.sql.SQLException: The class 'DummyVTI' does not exist or is inaccessible. This can happen if the class is not public.
> 	at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedStatement.executeQuery(Unknown Source)
> 	at org.apache.derbyTesting.functionTests.tests.lang.DatabaseClassLoadingTest.testTableFunctionInJar(DatabaseClassLoadingTest.java:1045)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:105)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> Caused by: java.sql.SQLException: Java exception: 'DummyVTI : DummyVTI (Unsupported major.minor version 49.0): java.lang.ClassNotFoundException'.
> 	at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> 	... 38 more
> Caused by: java.lang.ClassNotFoundException: DummyVTI : DummyVTI (Unsupported major.minor version 49.0)
> 	at org.apache.derby.impl.services.reflect.DatabaseClasses.loadApplicationClass(Unknown Source)
> 	at org.apache.derby.iapi.services.loader.ClassInspector.getClass(Unknown Source)
> 	at org.apache.derby.iapi.services.loader.ClassInspector.accessible(Unknown Source)
> 	at org.apache.derby.impl.sql.compile.QueryTreeNode.verifyClassExist(Unknown Source)
> 	at org.apache.derby.impl.sql.compile.StaticMethodCallNode.bindExpression(Unknown Source)
> 	at org.apache.derby.impl.sql.compile.JavaToSQLValueNode.bindExpression(Unknown Source)
> 	at org.apache.derby.impl.sql.compile.ResultColumn.bindExpression(Unknown Source)
> 	at org.apache.derby.impl.sql.compile.ResultColumnList.bindExpressions(Unknown Source)
> 	at org.apache.derby.impl.sql.compile.RowResultSetNode.bindExpressions(Unknown Source)
> 	at org.apache.derby.impl.sql.compile.DMLStatementNode.bindExpressions(Unknown Source)
> 	at org.apache.derby.impl.sql.compile.DMLStatementNode.bind(Unknown Source)
> 	at org.apache.derby.impl.sql.compile.CursorNode.bindStatement(Unknown Source)
> 	at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source)
> 	at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source)
> 	at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown Source)
> 	... 34 more

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