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] Resolved: (DERBY-3727) Improve error information reported when encountering "ERROR XSDB3: Container information cannot change once written: was 103, now 80"
Date Wed, 30 Jun 2010 17:11:49 GMT

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

Mike Matrigali resolved DERBY-3727.
-----------------------------------

    Fix Version/s: 10.7.0.0
       Resolution: Fixed

committed fix to trunk:
s1_ibm16:17>svn commit

Sending        java\engine\org\apache\derby\impl\store\raw\data\FileContainer.java
Sending        java\engine\org\apache\derby\impl\store\raw\data\RAFContainer.java
Sending        java\engine\org\apache\derby\loc\messages.xml
Sending        java\shared\org\apache\derby\shared\common\reference\SQLState.java
Sending        java\testing\org\apache\derbyTesting\functionTests\tests\lang\ErrorCodeTest.java
Transmitting file data .....
Committed revision 959378.

> Improve error information reported when encountering "ERROR XSDB3: Container information
cannot change once written: was 103, now 80"
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3727
>                 URL: https://issues.apache.org/jira/browse/DERBY-3727
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.4.1.3
>            Reporter: Mike Matrigali
>            Assignee: Mike Matrigali
>            Priority: Minor
>             Fix For: 10.7.0.0
>
>
> Improve the text associated with ERROR XSDB3: Container information cannot change once
written: was 103, now 80.  It would be nice to know which
> database and container at least, and possibly any other info that may have changed. 
Maybe page/hex dumps to track down overlapping I/O errors on page 0.
> Here is a stack trace reported as part of DERBY-3607, as encountered by a back ground
thread:
> 2008-06-12 08:53:12.421 GMT Thread[derby.rawStoreDaemon,5,derby.daemons] Cleanup action
starting^M
> ERROR XSDB3: Container information cannot change once written: was 103, now 80^M
>     at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)^M
>     at org.apache.derby.impl.store.raw.data.AllocPage.WriteContainerInfo(Unknown Source)^M
>     at org.apache.derby.impl.store.raw.data.FileContainer.writeHeader(Unknown Source)^M
>     at org.apache.derby.impl.store.raw.data.RAFContainer.writeRAFHeader(Unknown Source)^M
>     at org.apache.derby.impl.store.raw.data.RAFContainer.clean(Unknown Source)^M
>     at org.apache.derby.impl.services.cache.ConcurrentCache.cleanAndUnkeepEntry(Unknown
Source)^M
>     at org.apache.derby.impl.services.cache.ConcurrentCache.cleanEntry(Unknown Source)^M
>     at org.apache.derby.impl.services.cache.BackgroundCleaner.performWork(Unknown Source)^M
>     at org.apache.derby.impl.services.daemon.BasicDaemon.serviceClient(Unknown Source)^M
>     at org.apache.derby.impl.services.daemon.BasicDaemon.work(Unknown Source)^M
>     at org.apache.derby.impl.services.daemon.BasicDaemon.run(Unknown Source)^M
>     at java.lang.Thread.run(Unknown Source)^M

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