Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B3813106A5 for ; Thu, 20 Jun 2013 19:54:20 +0000 (UTC) Received: (qmail 62021 invoked by uid 500); 20 Jun 2013 19:54:20 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 62005 invoked by uid 500); 20 Jun 2013 19:54:20 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 61997 invoked by uid 99); 20 Jun 2013 19:54:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jun 2013 19:54:20 +0000 Date: Thu, 20 Jun 2013 19:54:20 +0000 (UTC) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DERBY-5988) Instability in DataSourceTest: some test fixture orderings makes test_jdbc4_1 fail MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-5988: --------------------------------- Urgency: Normal Labels: derby_triage10_11 (was: ) Has this bug been fixed now? > Instability in DataSourceTest: some test fixture orderings makes test_jdbc4_1 fail > ---------------------------------------------------------------------------------- > > Key: DERBY-5988 > URL: https://issues.apache.org/jira/browse/DERBY-5988 > Project: Derby > Issue Type: Bug > Components: JDBC, Services > Reporter: Dag H. Wanvik > Priority: Minor > Labels: derby_triage10_11 > Attachments: DataSourceTest.java > > > If this test fixture is executed before the driver is loaded the first time, a call to EmbeddedDataSource40.getParentLogger will fail with this symptom: > org.apache.derby.impl.jdbc.EmbedSQLException cannot be cast to java.sql.SQLFeatureNotSupportedException > at org.apache.derby.jdbc.EmbeddedDataSource40.getParentLogger(EmbeddedDataSource40.java:193) > at org.apache.derbyTesting.functionTests.tests.jdbc4.Wrapper41DataSource.getParentLogger(Wrapper41DataSource.java:81) > at org.apache.derbyTesting.functionTests.tests.jdbc4.DataSourceTest.vetDSjdbc4_1(DataSourceTest.java:318) > at org.apache.derbyTesting.functionTests.tests.jdbc4.DataSourceTest.test_jdbc4_1(DataSourceTest.java:307) > 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:117) > at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:424) > at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:441) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira