db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2755) logChecksumSetup fails with AssertFailure when 10.2 test is run against 10.3 server
Date Wed, 06 Jun 2007 20:49:26 GMT

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

Mike Matrigali updated DERBY-2755:

    Derby Info: [Existing Application Impact, Regression]  (was: [Regression, Existing Application

I haven't had time to set up my environment to reproduce this.  Is there a description exactly
how to get my environment set up to 
run 10.2 tests against  10.3.  Do I need to be running jars or can I do it in my normal classes
environment?  Do I just copy  some
10.2 jar file and manipulate my path?

This particular test uses some magic to test what it wants to test.  In the property file
it sets up  the following module so that it
can by hand manipulate the log file to test checksum errors, not something we want to support
for users:

My guess is that something is going on with the way we do this in 10.2 vs. 10.3, but this
is just a guess based on the limited
stack/error trace and the "wierd" thing that this test does.  The failure is happening right
when we are doing the very first 
connection for the create of this database so hardly anything special has happened yet other
than this property.  

Note the "csf" in the assert message string above is refering to the "corrupt storage factory".

I looked a bit but couldn't tell from some diffs why the test  is not running.  I vaguely
remember some discussion on the list about subSub protocols but don't remember for sure. 
  I am planning on checking in an improvement to the assert message so we can at least see
what the 2 strings it is comparing are.

> logChecksumSetup fails with  AssertFailure when 10.2 test is run against 10.3 server

> -------------------------------------------------------------------------------------
>                 Key: DERBY-2755
>                 URL: https://issues.apache.org/jira/browse/DERBY-2755
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:
>            Reporter: Kathey Marsden
>             Fix For:
> Here is the assertion running derbytesting.jar store/logChecksumSetup against
10.3 server. Several other tests failed because of the setup failure.
> Assertion failure
> Exception in thread "main" java.sql.SQLException: Java exception: 'ASSERT FAILED csf:C:\test\derbyall\storeall\storerecovery\storerecovery\wombat:
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:45)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:88)
> at org.apache.derby.impl.jdbc.Util.javaException(Util.java:245)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(TransactionResourceImpl.java:403)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(TransactionResourceImpl.java:346)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(EmbedConnection.java:1549)
> at org.apache.derby.impl.jdbc.EmbedConnection.<init>(EmbedConnection.java:373)
> at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Driver30.java:80)
> at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.java:209)
> at org.apache.derby.jdbc.AutoloadedDriver.connect(AutoloadedDriver.java:117)
> at java.sql.DriverManager.getConnection(DriverManager.java:562)
> at java.sql.DriverManager.getConnection(DriverManager.java:155)
> at org.apache.derby.impl.tools.ij.util.startJBMS(util.java:505)
> at org.apache.derby.impl.tools.ij.util.startJBMS(util.java:585)
> at org.apache.derby.impl.tools.ij.util.startJBMS(util.java:566)
> at org.apache.derby.tools.ij.startJBMS(ij.java:143)
> at org.apache.derbyTesting.functionTests.tests.store.LogChecksumSetup.main(Unknown Source)
> Caused by: org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED csf:C:\test\derbyall\storeall\storerecovery\storerecovery\wombat
> at org.apache.derby.shared.common.sanity.SanityManager.ASSERT(SanityManager.java:120)
> at org.apache.derby.impl.services.monitor.StorageFactoryService$10.run(StorageFactoryService.java:739)
> at java.security.AccessController.doPrivileged(AccessController.java:242)
> at org.apache.derby.impl.services.monitor.StorageFactoryService.removeServiceRoot(StorageFactoryService.java:729)
> at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1865)
> at org.apache.derby.impl.services.monitor.BaseMonitor.createPersistentService(BaseMonitor.java:1017)
> at org.apache.derby.iapi.services.monitor.Monitor.createPersistentService(Monitor.java:588)
> at org.apache.derby.impl.jdbc.EmbedConnection.createDatabase(EmbedConnection.java:1773)
> at org.apache.derby.impl.jdbc.EmbedConnection.<init>(EmbedConnection.java:281)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message