db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5988) Instability in DataSourceTest: some test fixture orderings makes test_jdbc4_1 fail
Date Mon, 12 Nov 2012 00:41:11 GMT

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

Dag H. Wanvik commented on DERBY-5988:
--------------------------------------

For client, the corresponding issue happens not in Util, but rather in org.apache.derby.client.am.SqlException#exceptionFactory:
the call org.apache.derby.client.am.SqlException#setExceptionFactory is missing unless we
load the client driver cf this call in ClinetDriver:

conn = (org.apache.derby.client.net.NetConnection)getFactory().
                    newNetConnection((org.apache.derby.client.net.NetLogWriter) 
                    dncLogWriter,
                    java.sql.DriverManager.getLoginTimeout(),
                    server,
                    port,
                    database,
                    augmentedProperties);

Note the call to "getFactory" here, which makes sure the right factory is initialized, cf.
ClientDriver#createJDBC40FactoryImpl called from getFactory.

So, the same problem is present for both drivers.
                
> 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
>         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

Mime
View raw message