db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (DERBY-3306) jdbc4.StatementEventsTest cannot be run individually in a clean environment
Date Wed, 20 Feb 2008 08:51:43 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan reopened DERBY-3306:
------------------------------------


Reopening to back out what I believe was an inappropriate change ('derby-3306-1c-create_db_by_default_and_test_fixes.diff
', revision 620480).
This commit caused a test regression on the J2ME platform, and it also brings along some unneeded
complexity in the JUnit framework.
The commit was done on the false assumption that there were many tests that had the same problem
as jdbc4.StatementEventsTest, but after writing a script to run every test individually I
found out that test is the only one.

Since the commit cannot be backed out cleanly (a test has been split into two files), I will
attach a patch that backs out the changes, fixes the jdbc4.StatementEventsTest and resolves
the test regression logged as DERBY-3412.

> jdbc4.StatementEventsTest cannot be run individually in a clean environment
> ---------------------------------------------------------------------------
>
>                 Key: DERBY-3306
>                 URL: https://issues.apache.org/jira/browse/DERBY-3306
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.4.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>         Attachments: derby-3306-1a-create_db_by_default.diff, derby-3306-1b-create_db_by_default_and_test_fixes.diff,
derby-3306-1b-create_db_by_default_and_test_fixes.stat, derby-3306-1c-create_db_by_default_and_test_fixes.diff,
derby-3306-errors_with_patch_1a.txt
>
>
> jdbc4.StatementEventsTest cannot be run individually in a clean environment because the
test database is not created if it does not exist.
> Excerpt of output from JUnit:
> 32) testErrorEventOnClosedConnection_pooled_prepared(org.apache.derbyTesting.functionTests.tests.jdbc4.StatementEventsTest)java.sql.SQLNonTransientConnectionException:
The connection was refused because the database wombat was not found.
>         at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70)
>         at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362)
>         at org.apache.derby.client.ClientPooledConnection.<init>(ClientPooledConnection.java:89)
>         at org.apache.derby.client.ClientPooledConnection40.<init>(ClientPooledConnection40.java:47)
>         at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newClientPooledConnection(ClientJDBCObjectFactoryImpl40.java:73)
>         at org.apache.derby.jdbc.ClientConnectionPoolDataSource.getPooledConnectionX(ClientConnectionPoolDataSource.java:100)
>         at org.apache.derby.jdbc.ClientConnectionPoolDataSource.getPooledConnection(ClientConnectionPoolDataSource.java:63)
>         at org.apache.derbyTesting.functionTests.tests.jdbc4.StatementEventsTest.setUp(StatementEventsTest.java:125)
>         at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:96)
>         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)
>         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)
> Caused by: org.apache.derby.client.am.DisconnectException: The connection was refused
because the database wombat was not found.
>         at org.apache.derby.client.net.NetConnectionReply.parseRDBNFNRM(NetConnectionReply.java:1022)
>         at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(NetConnectionReply.java:448)
>         at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(NetConnectionReply.java:306)
>         at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(NetConnectionReply.java:133)
>         at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java:887)
>         at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:799)
>         at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(NetConnection.java:620)
>         at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:435)
>         at org.apache.derby.client.net.NetConnection.initialize(NetConnection.java:296)
>         at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:280)
>         at org.apache.derby.client.net.NetConnection40.<init>(NetConnection40.java:125)
>         at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(ClientJDBCObjectFactoryImpl40.java:260)
>         at org.apache.derby.client.ClientPooledConnection.<init>(ClientPooledConnection.java:75)
>         ... 29 more
> FAILURES!!!
> Tests run: 32,  Failures: 0,  Errors: 32

-- 
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