You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Kathey Marsden <km...@sbcglobal.net> on 2009/04/06 18:56:59 UTC

10.4 -> 10.5 hard upgrade run

I hard upgraded a 10.4.2.0  database to 10.5.1.0 (RC) and ran 10.5 tests 
against it.  I hit only two instances of  DERBY-4127 and one replication 
failure which seems familar and I think is a known  intermittent issue, 
but I couldn't find an exact match in Jira.  The test 
testReplication_Local_StateTest_part1 passed on rerun. Should I file an 
issue for this or am I just putting in the wrong search criteria?

Thanks

Kathey



1) 
testGetColumnsReadOnly(org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest)java.lang.ArrayIndexOutOfBoundsException
    at org.apache.derby.client.net.NetCursor.readFdocaBytes(Unknown Source)
    at org.apache.derby.client.net.NetCursor.parseSQLCAXGRP(Unknown Source)
    at org.apache.derby.client.net.NetCursor.parseSQLCAGRP(Unknown Source)
    at org.apache.derby.client.net.NetCursor.parseSQLCARD(Unknown Source)
    at 
org.apache.derby.client.net.NetCursor.calculateColumnOffsetsForRow_(Unknown 
Source)
    at org.apache.derby.client.am.Cursor.stepNext(Unknown Source)
    at 
org.apache.derby.client.net.NetCursor.scanDataBufferForEndOfData(Unknown 
Source)
    at org.apache.derby.client.net.NetResultSet.preClose_(Unknown Source)
    at org.apache.derby.client.am.ResultSet.closeX(Unknown Source)
    at org.apache.derby.client.am.ResultSet.close(Unknown Source)
    at 
org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest.crossCheckGetColumnsAndResultSetMetaData(DatabaseMetaDataTest.java:1692)
    at 
org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest.testGetColumnsReadOnly(DatabaseMetaDataTest.java:1389)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at 
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:105)
    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
    at junit.extensions.TestSetup.run(TestSetup.java:23)
    at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
    at junit.extensions.TestSetup.run(TestSetup.java:23)
    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
    at junit.extensions.TestSetup.run(TestSetup.java:23)
    at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
2) 
testGetColumnsModify(org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest)java.lang.ArrayIndexOutOfBoundsException
    at org.apache.derby.client.net.NetCursor.readFdocaBytes(Unknown Source)
    at org.apache.derby.client.net.NetCursor.parseSQLCAXGRP(Unknown Source)
    at org.apache.derby.client.net.NetCursor.parseSQLCAGRP(Unknown Source)
    at org.apache.derby.client.net.NetCursor.parseSQLCARD(Unknown Source)
    at 
org.apache.derby.client.net.NetCursor.calculateColumnOffsetsForRow_(Unknown 
Source)
    at org.apache.derby.client.am.Cursor.stepNext(Unknown Source)
    at 
org.apache.derby.client.net.NetCursor.scanDataBufferForEndOfData(Unknown 
Source)
    at org.apache.derby.client.net.NetResultSet.preClose_(Unknown Source)
    at org.apache.derby.client.am.ResultSet.closeX(Unknown Source)
    at org.apache.derby.client.am.ResultSet.close(Unknown Source)
    at 
org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest.crossCheckGetColumnsAndResultSetMetaData(DatabaseMetaDataTest.java:1692)
    at 
org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest.testGetColumnsReadOnly(DatabaseMetaDataTest.java:1389)
    at 
org.apache.derbyTesting.functionTests.tests.jdbcapi.DatabaseMetaDataTest.testGetColumnsModify(DatabaseMetaDataTest.java:1406)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at 
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:105)
    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
    at junit.extensions.TestSetup.run(TestSetup.java:23)
    at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
    at junit.extensions.TestSetup.run(TestSetup.java:23)
    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
    at junit.extensions.TestSetup.run(TestSetup.java:23)
    at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
There was 1 failure:
1) 
testReplication_Local_StateTest_part1(org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_StateTest_part1)junit.framework.ComparisonFailure: 
Unexpected SQL state. expected:<...20> but was:<...07>
    at 
org.apache.derbyTesting.junit.BaseJDBCTestCase.assertSQLState(BaseJDBCTestCase.java:760)
    at 
org.apache.derbyTesting.junit.BaseJDBCTestCase.assertSQLState(BaseJDBCTestCase.java:809)
    at 
org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.failOver_direct(ReplicationRun.java:1381)
    at 
org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.failOver(ReplicationRun.java:1302)
    at 
org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_StateTest_part1.testReplication_Local_StateTest_part1(ReplicationRun_Local_StateTest_part1.java:160)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at 
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:105)
    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
    at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: java.sql.SQLException: DERBY SQL error: SQLCODE: -1, 
SQLSTATE: XRE07, SQLERRMC: Could not perform operation because the 
database is not in replication master mode.
    at 
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown 
Source)
    at org.apache.derby.client.am.SqlException.getSQLException(Unknown 
Source)
    at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
    at java.sql.DriverManager.getConnection(DriverManager.java:316)
    at java.sql.DriverManager.getConnection(DriverManager.java:273)
    at 
org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.failOver_direct(ReplicationRun.java:1368)
    ... 28 more
Caused by: org.apache.derby.client.am.SqlException: DERBY SQL error: 
SQLCODE: -1, SQLSTATE: XRE07, SQLERRMC: Could not perform operation 
because the database is not in replication master mode.
    at org.apache.derby.client.am.Connection.completeSqlca(Unknown Source)
    at 
org.apache.derby.client.net.NetConnectionReply.parseRdbAccessFailed(Unknown 
Source)
    at 
org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(Unknown 
Source)
    at 
org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(Unknown 
Source)
    at 
org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(Unknown 
Source)
    at 
org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(Unknown 
Source)
    at 
org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(Unknown 
Source)
    at 
org.apache.derby.client.net.NetConnection.flowUSRIDONLconnect(Unknown 
Source)
    at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source)
    at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
    at org.apache.derby.client.net.NetConnection40.<init>(Unknown Source)
    at 
org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(Unknown 
Source)
    ... 32 more

FAILURES!!!
Tests run: 10939,  Failures: 1,  Errors: 2


Re: 10.4 -> 10.5 hard upgrade run

Posted by Kathey Marsden <km...@sbcglobal.net>.
Knut Anders Hatlen wrote:
> If I read the stack trace you provided from derby.log correctly, that
> error did not happen in the replication tests, but in the upgrade tests:
>
>   
Good point.  I think I have been trying to do too many things at once 
and not looking carefully.  So, do the replication tests not use 
system/wombat at all?  If that's the case, then perhaps the failure is 
unrelated to upgrade even though I saw it twice in a row.

Below is the only thing of interest in db_slave/derby.log:

ERROR XRE43: Unexpected error when trying to stop replication slave 
mode. To stop repliation slave mode, use operation 'stopSlave' or 
'failover'.

    at 
org.apache.derby.iapi.error.StandardException.newException(Unknown Source)

    at 
org.apache.derby.impl.db.SlaveDatabase.verifyShutdownSlave(Unknown Source)

    at 
org.apache.derby.impl.jdbc.EmbedConnection.internalStopReplicationSlave(Unknown 
Source)

    at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)

    at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)

    at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)

    at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)

    at org.apache.derby.impl.drda.Database.makeConnection(Unknown Source)

    at 
org.apache.derby.impl.drda.DRDAConnThread.getConnFromDatabaseName(Unknown 
Source)

    at 
org.apache.derby.impl.drda.DRDAConnThread.verifyUserIdPassword(Unknown 
Source)

    at org.apache.derby.impl.drda.DRDAConnThread.parseSECCHK(Unknown Source)

    at 
org.apache.derby.impl.drda.DRDAConnThread.parseDRDAConnection(Unknown 
Source)

    at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown 
Source)

    at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)

Cleanup action completed

2009-04-06 19:12:16.375 GMT Thread[DRDAConnThread_7,5,main] (DATABASE = 
C:\test4\db_slave\wombat), (DRDAID = {4}), Unexpected error when trying 
to stop replication slave mode. To stop repliation slave mode, use 
operation 'stopSlave' or 'failover'.

   I can't really correlate it to the failing test though. The exception 
the test reported does not seem to be in either log.  Perhaps the logs 
were overwritten by other tests or perhaps it is just one of those 
errors that doesn't get logged.

Kathey


Re: 10.4 -> 10.5 hard upgrade run

Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
Kathey Marsden <km...@sbcglobal.net> writes:

> Ole Solberg wrote:
>> On 04/07/09 00:07, Kathey Marsden wrote:
>>> Kathey Marsden wrote:
>>>> Myrna van Lunteren wrote:
>>>>> Could this be another manifestation of DERBY-3719?
>>>>>
>>>>> That bug doesn't show the entire stack for the test failure, and it's
>>>>> on a different test, but the error seems similar...
>>>>>
>>>>> Myrna
>>>>>
>>>>>   
>>>> Thanks Myrna,
>>>>
>>>> I accidentally blew away my results on rerun, so can't confirm the
>>>> LogBufferFullException, but we'll just assume for now it is the
>>>> same as DERBY-3719, unless I can reproduce again and find a
>>>> different root cause. I'll put a comment in the issue.
>>>>
>>> I did another 10.4 -> 10.5 hard upgrade run and again got the same
>>> failure in the same test (testReplication_Local_StateTest_part1)
>>> This time I was able to retrieve the derby.log and am wondering if
>>> maybe it is something different than DERBY-3719.  I see this errror
>>> in the derby.log  The interesting thing is that it is complaining
>>> about the singleUse\oneuse7c database and that one is created by
>>> the test and so was not hard upgraded.  I only premade wombat.
>>>
>>> Caused by: ERROR XSLAN: Database at
>>> C:\test4\system\singleUse\oneuse7c has an incompatible format with
>>> the current version of the software.  The database was created by
>>> or upgraded by version 10.5.
>>>
>> .
>> .
>>>
>>>
>>
>> I have tried looking for a similar case in our testing ....
>>
>> Was this seen in a db_master/derby.log or db_slave/derby.log?
>>
>> The replication tests creates its test databases for each testcase
>> and puts its derby.log files in db_master/ and db_slave/.
>>
> After the run, I saw the error in
> fail/Embedded_40/ReplicationRun_Local_StateTest_part1/testReplication_Local_StateTest_part1/derby.log
>
> I don't see it in the db_master or db_slave derby.log files.

If I read the stack trace you provided from derby.log correctly, that
error did not happen in the replication tests, but in the upgrade tests:

>>>    at
>>> org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.noConnectionAfterHardUpgrade(BasicSetup.java:197)

Since we copy the entire derby.log on error, it is possible that errors
from earlier tests show up. (I think the replication tests run after the
upgrade tests.)

-- 
Knut Anders

Re: 10.4 -> 10.5 hard upgrade run

Posted by Kathey Marsden <km...@sbcglobal.net>.
Ole Solberg wrote:
> On 04/07/09 00:07, Kathey Marsden wrote:
>> Kathey Marsden wrote:
>>> Myrna van Lunteren wrote:
>>>> Could this be another manifestation of DERBY-3719?
>>>>
>>>> That bug doesn't show the entire stack for the test failure, and it's
>>>> on a different test, but the error seems similar...
>>>>
>>>> Myrna
>>>>
>>>>   
>>> Thanks Myrna,
>>>
>>> I accidentally blew away my results on rerun, so can't confirm the 
>>> LogBufferFullException, but we'll just assume for now it is the same 
>>> as DERBY-3719, unless I can reproduce again and find a different 
>>> root cause. I'll put a comment in the issue.
>>>
>> I did another 10.4 -> 10.5 hard upgrade run and again got the same 
>> failure in the same test (testReplication_Local_StateTest_part1)  
>> This time I was able to retrieve the derby.log and am wondering if 
>> maybe it is something different than DERBY-3719.  I see this errror 
>> in the derby.log  The interesting thing is that it is complaining 
>> about the singleUse\oneuse7c database and that one is created by the 
>> test and so was not hard upgraded.  I only premade wombat.
>>
>> Caused by: ERROR XSLAN: Database at 
>> C:\test4\system\singleUse\oneuse7c has an incompatible format with 
>> the current version of the software.  The database was created by or 
>> upgraded by version 10.5.
>>
> .
> .
>>
>>
>
> I have tried looking for a similar case in our testing ....
>
> Was this seen in a db_master/derby.log or db_slave/derby.log?
>
> The replication tests creates its test databases for each testcase and 
> puts its derby.log files in db_master/ and db_slave/.
>
After the run, I saw the error in
fail/Embedded_40/ReplicationRun_Local_StateTest_part1/testReplication_Local_StateTest_part1/derby.log

I don't see it in the db_master or db_slave derby.log files.


Re: 10.4 -> 10.5 hard upgrade run

Posted by Ole Solberg <Ol...@Sun.COM>.
On 04/07/09 00:07, Kathey Marsden wrote:
> Kathey Marsden wrote:
>> Myrna van Lunteren wrote:
>>> Could this be another manifestation of DERBY-3719?
>>>
>>> That bug doesn't show the entire stack for the test failure, and it's
>>> on a different test, but the error seems similar...
>>>
>>> Myrna
>>>
>>>   
>> Thanks Myrna,
>>
>> I accidentally blew away my results on rerun, so can't confirm the 
>> LogBufferFullException, but we'll just assume for now it is the same 
>> as DERBY-3719, unless I can reproduce again and find a different root 
>> cause. I'll put a comment in the issue.
>>
> I did another 10.4 -> 10.5 hard upgrade run and again got the same 
> failure in the same test (testReplication_Local_StateTest_part1)  This 
> time I was able to retrieve the derby.log and am wondering if maybe it 
> is something different than DERBY-3719.  I see this errror in the 
> derby.log  The interesting thing is that it is complaining about the 
> singleUse\oneuse7c database and that one is created by the test and so 
> was not hard upgraded.  I only premade wombat.
> 
> Caused by: ERROR XSLAN: Database at C:\test4\system\singleUse\oneuse7c 
> has an incompatible format with the current version of the software.  
> The database was created by or upgraded by version 10.5.
> 
.
.
> 
> 

I have tried looking for a similar case in our testing ....

Was this seen in a db_master/derby.log or db_slave/derby.log?

The replication tests creates its test databases for each testcase and 
puts its derby.log files in db_master/ and db_slave/.

The repl. tests currently do not test replication after upgrade or 
upgrade on a replicated db - should probably be added though.



-- 
Ole Solberg, Database Technology Group,
Sun Microsystems, Trondheim, Norway

Re: 10.4 -> 10.5 hard upgrade run

Posted by Kathey Marsden <km...@sbcglobal.net>.
Kathey Marsden wrote:
> Myrna van Lunteren wrote:
>> Could this be another manifestation of DERBY-3719?
>>
>> That bug doesn't show the entire stack for the test failure, and it's
>> on a different test, but the error seems similar...
>>
>> Myrna
>>
>>   
> Thanks Myrna,
>
> I accidentally blew away my results on rerun, so can't confirm the 
> LogBufferFullException, but we'll just assume for now it is the same 
> as DERBY-3719, unless I can reproduce again and find a different root 
> cause. I'll put a comment in the issue.
>
I did another 10.4 -> 10.5 hard upgrade run and again got the same 
failure in the same test (testReplication_Local_StateTest_part1)  This 
time I was able to retrieve the derby.log and am wondering if maybe it 
is something different than DERBY-3719.  I see this errror in the 
derby.log  The interesting thing is that it is complaining about the 
singleUse\oneuse7c database and that one is created by the test and so 
was not hard upgraded.  I only premade wombat.

Caused by: ERROR XSLAN: Database at C:\test4\system\singleUse\oneuse7c 
has an incompatible format with the current version of the software.  
The database was created by or upgraded by version 10.5.

    at 
org.apache.derby.iapi.error.StandardException.newException(Unknown Source)

    at 
org.apache.derby.impl.store.raw.log.LogToFile.readControlFile(Unknown 
Source)

    at org.apache.derby.impl.store.raw.log.LogToFile.boot(Unknown Source)

    at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown 
Source)

    at 
org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)

    at 
org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown 
Source)

    at 
org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown 
Source)

    at 
org.apache.derby.impl.store.raw.data.BaseDataFileFactory.bootLogFactory(Unknown 
Source)

    at 
org.apache.derby.impl.store.raw.data.BaseDataFileFactory.setRawStoreFactory(Unknown 
Source)

    at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)

    at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown 
Source)

    at 
org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)

    at 
org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown 
Source)

    at 
org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown 
Source)

    at org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown 
Source)

    at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown 
Source)

    at 
org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)

    at 
org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown 
Source)

    at 
org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown 
Source)

    at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown Source)

    at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)

    at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown 
Source)

    at 
org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)

    at 
org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown 
Source)

    at 
org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService(Unknown 
Source)

    at 
org.apache.derby.impl.services.monitor.BaseMonitor.findProviderAndStartService(Unknown 
Source)

    at 
org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService(Unknown 
Source)

    at 
org.apache.derby.iapi.services.monitor.Monitor.startPersistentService(Unknown 
Source)

    ... 97 more

============= end nested exception, level (1) ===========

============= begin nested exception, level (2) ===========

java.sql.SQLException: Database at C:\test4\system\singleUse\oneuse7c 
has an incompatible format with the current version of the software.  
The database was created by or upgraded by version 10.5.

    at 
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown 
Source)

    at 
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown 
Source)

    at 
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown 
Source)

    at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown 
Source)

    at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown 
Source)

    at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)

    at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)

    at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)

    at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(Unknown 
Source)

    at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(Unknown 
Source)

    at 
org.apache.derbyTesting.junit.DataSourceConnector.openConnection(DataSourceConnector.java:54)

    at 
org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:1314)

    at 
org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:419)

    at 
org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:95)

    at 
org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.noConnectionAfterHardUpgrade(BasicSetup.java:197)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)

    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

    at java.lang.reflect.Method.invoke(Method.java:599)

    at junit.framework.TestCase.runTest(TestCase.java:154)

    at junit.framework.TestCase.runBare(TestCase.java:127)

    at 
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:105)

    at junit.framework.TestResult$1.protect(TestResult.java:106)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.framework.TestResult.run(TestResult.java:103)

    at junit.framework.TestCase.run(TestCase.java:118)

    at junit.framework.TestSuite.runTest(TestSuite.java:208)

    at junit.framework.TestSuite.run(TestSuite.java:203)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:51)

    at junit.framework.TestSuite.runTest(TestSuite.java:208)

    at junit.framework.TestSuite.run(TestSuite.java:203)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:51)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:51)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:51)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:51)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:51)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)

    at junit.extensions.TestSetup$1.protect(TestSetup.java:19)

    at junit.framework.TestResult.runProtected(TestResult.java:124)

    at junit.extensions.TestSetup.run(TestSetup.java:23)

    at junit.framework.TestSuite.runTest(TestSuite.java:208)

    at junit.framework.TestSuite.run(TestSuite.java:203)

    at junit.framework.TestSuite.runTest(TestSuite.java:208)

    at junit.framework.TestSuite.run(TestSuite.java:203)

    at junit.framework.TestSuite.runTest(TestSuite.java:208)

    at junit.framework.TestSuite.run(TestSuite.java:203)

    at junit.textui.TestRunner.doRun(TestRunner.java:116)

    at junit.textui.TestRunner.start(TestRunner.java:172)

    at junit.textui.TestRunner.main(TestRunner.java:138)



Re: 10.4 -> 10.5 hard upgrade run

Posted by Kathey Marsden <km...@sbcglobal.net>.
Myrna van Lunteren wrote:
> Could this be another manifestation of DERBY-3719?
>
> That bug doesn't show the entire stack for the test failure, and it's
> on a different test, but the error seems similar...
>
> Myrna
>
>   
Thanks Myrna,

I accidentally blew away my results on rerun, so can't confirm the 
LogBufferFullException, but we'll just assume for now it is the same as 
DERBY-3719, unless I can reproduce again and find a different root 
cause. I'll put a comment in the issue.


Thanks

Kathey


Re: 10.4 -> 10.5 hard upgrade run

Posted by Myrna van Lunteren <m....@gmail.com>.
Could this be another manifestation of DERBY-3719?

That bug doesn't show the entire stack for the test failure, and it's
on a different test, but the error seems similar...

Myrna