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 "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/01/09 01:06:27 UTC
[jira] Created: (DERBY-2221) Cannot re-connect to 10.0 database
after soft upgrade with 10.3 (trunk) code
Cannot re-connect to 10.0 database after soft upgrade with 10.3 (trunk) code
----------------------------------------------------------------------------
Key: DERBY-2221
URL: https://issues.apache.org/jira/browse/DERBY-2221
Project: Derby
Issue Type: Bug
Affects Versions: 10.3.0.0
Reporter: Daniel John Debrunner
Database fails to start with 10.0.2.1 after a 10.3 database has connected to it. Caused by a NullPointerException.
Even if 10.0 is not a common starting point it would be good to track down what is causing this, it seems to be some on-disk format
of an object has changed in an incompatible way.
To reproduce run the JUnit upgrade test added by DERBY-2217
org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite
setting the system property derbyTesting.jar.path to point to a folder that contains a 10.0.2.1 release in the folder 10.0.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-2221) Cannot re-connect to 10.0 database
after soft upgrade with 10.3 (trunk) code
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali reassigned DERBY-2221:
-------------------------------------
Assignee: Mike Matrigali
> Cannot re-connect to 10.0 database after soft upgrade with 10.3 (trunk) code
> ----------------------------------------------------------------------------
>
> Key: DERBY-2221
> URL: https://issues.apache.org/jira/browse/DERBY-2221
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Mike Matrigali
>
> Database fails to start with 10.0.2.1 after a 10.3 database has connected to it. Caused by a NullPointerException.
> Even if 10.0 is not a common starting point it would be good to track down what is causing this, it seems to be some on-disk format
> of an object has changed in an incompatible way.
> To reproduce run the JUnit upgrade test added by DERBY-2217
> org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite
> setting the system property derbyTesting.jar.path to point to a folder that contains a 10.0.2.1 release in the folder 10.0.2.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2221) Cannot re-connect to 10.0 database
after soft upgrade with 10.3 (trunk) code
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463169 ]
Daniel John Debrunner commented on DERBY-2221:
----------------------------------------------
Stack trace is:
java.sql.SQLException: Failed to start database 'singleUse/oneuse0', see the next exception for details.
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.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(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.Driver30.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.functionTests.tests.upgradeTests.PhaseChanger.setUp(PhaseChanger.java:94)
at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
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.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.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.swingui.TestRunner$16.run(TestRunner.java:623)
java.lang.NullPointerException
at org.apache.derby.iapi.services.io.FormatableHashtable.getInt(Unknown Source)
at org.apache.derby.iapi.services.io.FormatableHashtable.getBoolean(Unknown Source)
at org.apache.derby.impl.sql.GenericColumnDescriptor.readExternal(Unknown Source)
at org.apache.derby.iapi.services.io.FormatIdInputStream.readObject(Unknown Source)
at org.apache.derby.impl.sql.GenericResultDescription.readExternal(Unknown Source)
at org.apache.derby.iapi.services.io.FormatIdInputStream.readObject(Unknown Source)
at org.apache.derby.impl.sql.GenericStorablePreparedStatement.readExternal(Unknown Source)
at org.apache.derby.iapi.services.io.FormatIdInputStream.readObject(Unknown Source)
at org.apache.derby.iapi.types.UserType.readExternal(Unknown Source)
at org.apache.derby.impl.store.raw.data.StoredPage.readRecordFromArray(Unknown Source)
at org.apache.derby.impl.store.raw.data.StoredPage.restoreRecordFromSlot(Unknown Source)
at org.apache.derby.impl.store.raw.data.BasePage.fetchFromSlot(Unknown Source)
at org.apache.derby.impl.store.access.conglomerate.GenericScanController.fetchRows(Unknown Source)
at org.apache.derby.impl.store.access.heap.HeapScan.fetchNext(Unknown Source)
at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.getDescriptorViaHeap(Unknown Source)
at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.getAllSPSDescriptors(Unknown Source)
at org.apache.derby.impl.sql.catalog.DD_Version.dropJDBCMetadataSPSes(Unknown Source)
at org.apache.derby.impl.sql.catalog.DD_Version.doFullUpgrade(Unknown Source)
at org.apache.derby.impl.sql.catalog.DD_Version.upgradeIfNeeded(Unknown Source)
at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.loadDictionaryTables(Unknown Source)
at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.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.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)
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.Driver30.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.functionTests.tests.upgradeTests.PhaseChanger.setUp(PhaseChanger.java:94)
at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
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.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.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.swingui.TestRunner$16.run(TestRunner.java:623)
> Cannot re-connect to 10.0 database after soft upgrade with 10.3 (trunk) code
> ----------------------------------------------------------------------------
>
> Key: DERBY-2221
> URL: https://issues.apache.org/jira/browse/DERBY-2221
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
>
> Database fails to start with 10.0.2.1 after a 10.3 database has connected to it. Caused by a NullPointerException.
> Even if 10.0 is not a common starting point it would be good to track down what is causing this, it seems to be some on-disk format
> of an object has changed in an incompatible way.
> To reproduce run the JUnit upgrade test added by DERBY-2217
> org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite
> setting the system property derbyTesting.jar.path to point to a folder that contains a 10.0.2.1 release in the folder 10.0.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2221) Cannot re-connect to 10.0 database
after soft upgrade with 10.3 (trunk) code
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-2221:
----------------------------------
Component/s: SQL
Regression Test Failure
I am not seeing this issue. Currently (on truck as of change 535573) I only see DERBY-2612 which is not a null pointer error.
> Cannot re-connect to 10.0 database after soft upgrade with 10.3 (trunk) code
> ----------------------------------------------------------------------------
>
> Key: DERBY-2221
> URL: https://issues.apache.org/jira/browse/DERBY-2221
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure, SQL
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Mike Matrigali
>
> Database fails to start with 10.0.2.1 after a 10.3 database has connected to it. Caused by a NullPointerException.
> Even if 10.0 is not a common starting point it would be good to track down what is causing this, it seems to be some on-disk format
> of an object has changed in an incompatible way.
> To reproduce run the JUnit upgrade test added by DERBY-2217
> org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite
> setting the system property derbyTesting.jar.path to point to a folder that contains a 10.0.2.1 release in the folder 10.0.2.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-2221) Cannot re-connect to 10.0 database
after soft upgrade with 10.3 (trunk) code
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner closed DERBY-2221.
----------------------------------------
I rebuilt the jars files from svn revision 494201 which corresponds to the first working version of the JUnit upgrade tests and the version for this bug.
Running the 494201 tests failed on 10.0 and passed on all others as this bug states.
Changing to use a trunk version of derby.jar (from today) while continuing to use derbyTesting.jar from 494201 passed on all old versions including 10.0. I.e. no problem with the latest version of derby.
Thus I believe that this bug has been fixed by other changes.
> Cannot re-connect to 10.0 database after soft upgrade with 10.3 (trunk) code
> ----------------------------------------------------------------------------
>
> Key: DERBY-2221
> URL: https://issues.apache.org/jira/browse/DERBY-2221
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure, SQL
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Mike Matrigali
>
> Database fails to start with 10.0.2.1 after a 10.3 database has connected to it. Caused by a NullPointerException.
> Even if 10.0 is not a common starting point it would be good to track down what is causing this, it seems to be some on-disk format
> of an object has changed in an incompatible way.
> To reproduce run the JUnit upgrade test added by DERBY-2217
> org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite
> setting the system property derbyTesting.jar.path to point to a folder that contains a 10.0.2.1 release in the folder 10.0.2.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2221) Cannot re-connect to 10.0 database
after soft upgrade with 10.3 (trunk) code
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner updated DERBY-2221:
-----------------------------------------
Derby Info: [Regression]
Do not see this on 10.2.1.6 and 10.2.2.0 when running the upgradeTests._Suite with derbyTesting from 10.3 (trunk) and derby.jar from 10.2 (as the new version) in the classpath.
> Cannot re-connect to 10.0 database after soft upgrade with 10.3 (trunk) code
> ----------------------------------------------------------------------------
>
> Key: DERBY-2221
> URL: https://issues.apache.org/jira/browse/DERBY-2221
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
>
> Database fails to start with 10.0.2.1 after a 10.3 database has connected to it. Caused by a NullPointerException.
> Even if 10.0 is not a common starting point it would be good to track down what is causing this, it seems to be some on-disk format
> of an object has changed in an incompatible way.
> To reproduce run the JUnit upgrade test added by DERBY-2217
> org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite
> setting the system property derbyTesting.jar.path to point to a folder that contains a 10.0.2.1 release in the folder 10.0.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-2221) Cannot re-connect to 10.0 database
after soft upgrade with 10.3 (trunk) code
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali resolved DERBY-2221.
-----------------------------------
Resolution: Cannot Reproduce
I believe that the upgrade tests are now running successfully against 10.3 , testing upgrade from all previous releases. A
number of changes went in close together to get upgrade working against 10.3 . I never saw this exact stack while working
on those issues so I reported and fixed separate bugs to exactly document what I was fixing.
The bugs fixed to get the upgrade tests running in 10.3 trunk included:
DERBY-2611
DERBY-2612
DERBY-2613
DERBY-2598
> Cannot re-connect to 10.0 database after soft upgrade with 10.3 (trunk) code
> ----------------------------------------------------------------------------
>
> Key: DERBY-2221
> URL: https://issues.apache.org/jira/browse/DERBY-2221
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure, SQL
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Mike Matrigali
>
> Database fails to start with 10.0.2.1 after a 10.3 database has connected to it. Caused by a NullPointerException.
> Even if 10.0 is not a common starting point it would be good to track down what is causing this, it seems to be some on-disk format
> of an object has changed in an incompatible way.
> To reproduce run the JUnit upgrade test added by DERBY-2217
> org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite
> setting the system property derbyTesting.jar.path to point to a folder that contains a 10.0.2.1 release in the folder 10.0.2.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2221) Cannot re-connect to 10.0 database
after soft upgrade with 10.3 (trunk) code
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-2221:
---------------------------------
Bug behavior facts: [Regression, Regression Test Failure] (was: [Regression])
> Cannot re-connect to 10.0 database after soft upgrade with 10.3 (trunk) code
> ----------------------------------------------------------------------------
>
> Key: DERBY-2221
> URL: https://issues.apache.org/jira/browse/DERBY-2221
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.1.4
> Reporter: Daniel John Debrunner
> Assignee: Mike Matrigali
>
> Database fails to start with 10.0.2.1 after a 10.3 database has connected to it. Caused by a NullPointerException.
> Even if 10.0 is not a common starting point it would be good to track down what is causing this, it seems to be some on-disk format
> of an object has changed in an incompatible way.
> To reproduce run the JUnit upgrade test added by DERBY-2217
> org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite
> setting the system property derbyTesting.jar.path to point to a folder that contains a 10.0.2.1 release in the folder 10.0.2.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.