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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2009/03/25 18:02:54 UTC
[jira] Issue Comment Edited: (DERBY-4075) ERROR XSDBB: Unknown page
format at page Page(613,Container(0, 1024)) when running MailJdbc
(Embedded) system tests
[ https://issues.apache.org/jira/browse/DERBY-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689157#action_12689157 ]
Myrna van Lunteren edited comment on DERBY-4075 at 3/25/09 10:02 AM:
---------------------------------------------------------------------
I think I've run this test in its non-intended configuration (i.e. none of the properties as specified in the checked-in derby.properties) about 7 times with sane build and had failures, 5 on windows, 2 on linux. Only 2x did I see the XSDBB errors.
Findings so far:
- on my windows box, error shows up after 24-27 hours
(which effectively usually means I let it run for close to 2 days).
- on windows: 5x seen some corruption error
- on linux: 1 failure showed up after 15 hours.
- on linux: 1 failure just before disk space full. Still investigating this.
- any runs with logSeverityLevel=0/logStatementText were fine (ran for 3, 4 days before I killed it or it filled up the about 30G disk space I have available)
- runs with modified derbyTesting.jar (print timing as per patch): 1x no problems, 1 time some corruption error.
- insane build showed no errors.
- linux vs. windows error situation is quite different - may not be the same problem.
I'll do some more analysis of failing databases and log files, and kick off another test once I've run. And yes, I'll try with another jvm version. Note that I've run with different SR levels of the jvm on windows vs. linux. But I'll try a run with ibm15 and one with jdk16.
was (Author: myrna):
I think I've run this test in its non-intended configuration (i.e. none of the properties as specified in the checked-in derby.properties) about 7 times with insane build and had failures, 5 on windows, 2 on linux. Only 2x did I see the XSDBB errors.
Findings so far:
- on my windows box, error shows up after 24-27 hours
(which effectively usually means I let it run for close to 2 days).
- on windows: 5x seen some corruption error
- on linux: 1 failure showed up after 15 hours.
- on linux: 1 failure just before disk space full. Still investigating this.
- any runs with logSeverityLevel=0/logStatementText were fine (ran for 3, 4 days before I killed it or it filled up the about 30G disk space I have available)
- runs with modified derbyTesting.jar (print timing as per patch): 1x no problems, 1 time some corruption error.
- insane build showed no errors.
- linux vs. windows error situation is quite different - may not be the same problem.
I'll do some more analysis of failing databases and log files, and kick off another test once I've run. And yes, I'll try with another jvm version. Note that I've run with different SR levels of the jvm on windows vs. linux. But I'll try a run with ibm15 and one with jdk16.
> ERROR XSDBB: Unknown page format at page Page(613,Container(0, 1024)) when running MailJdbc (Embedded) system tests
> -------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4075
> URL: https://issues.apache.org/jira/browse/DERBY-4075
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.5.0.0
> Environment: windows 2000 professional, ibm 1.6 (sr2), revision 10.5: 745360
> Reporter: Myrna van Lunteren
> Priority: Blocker
> Fix For: 10.5.0.0
>
> Attachments: Activity.out, d4075_debugchange.diff, derby.log.run2, derbylog.zip, performance.out, windows5logout.jar
>
>
> I started the org.apache.derbyTesting.system.mailJdbc Embedded test and after about 1 day it ran into an apparently corrupted database.
> 2009-02-19 14:02:44.221 GMT Thread[Refresh Thread,5,main] (XID = 349909), (SESSIONID = 1), (DATABASE = mailsdb), (DRDAID = null), Failed Statement is: insert into REFRESH.INBOX(from_name,to_name,date,Message,attach_id,size_problem) values (?,?,?,?,?,?) with 6 parameters begin parameter #1: ABCE :end parameter begin parameter #2: WXYY :end parameter begin parameter #3: 2009-02-19 06:02:43.705 :end parameter begin parameter #4: CLOB(org.apache.derby.iapi.types.ReaderToUTF8Stream@41ba41ba) :end parameter begin parameter #5: 0 :end parameter begin parameter #6: This column is used only to by pass the space problem. If the problem still exists, then we are going to have a serious issue here.***************************************************************************************************** :end parameter
> ERROR XSDBB: Unknown page format at page Page(613,Container(0, 1024)), page dump follows: Hex dump:
> The error up to that point appear to me no different from other errors that this test is expected to produce (40001, 23505, 4XL01) except that the very first error is a grant error.
> I think we can't have a release until this corruption is explained away or fixed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.