[
https://issues.apache.org/jira/browse/DERBY-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682734#action_12682734
]
Myrna van Lunteren commented on DERBY-4075:
-------------------------------------------
Thank you, Kristian and Kathey, for running the test...
My latest attempts have shown no unexpected errors except the GRANT.
This setup different from the original in that
- I replace the derbyTesting.jar with a more recent one that also had the extra
time printing (as per my patch)
- added derby.properties:
derby.stream.error.logSeverityLevel=0
derby.language.logStatementText=true
Apparently, one of these differences makes the problem disappear.
I've also looked at the databases of the runs where there was some problem, and
in 2 cases I had no problem selecting from any of the tables (user tables and
system tables), and in the 2 cases where I got the XSDBB error once the
corrupted table was REFRESH.INBOX and the other REFRESH.ATTACH. In each case
the backed up database allowed select on all the tables.
I've run now on 2 machines. The failing situations were on:
- windows machine:
OS: Microsoft Windows 2000, service Pack 4
java: java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr2-20080607_01(SR2))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows 2000 x86-32
jvmwi3260-20080603_19964 (JIT enabled, AOT enabled)
J9VM - 20080603_019964_lHdSMr
JIT - r9_20080602_1330
GC - 20080603_AB)
JCL - 20080606_02
IBM eserver, Two cpu's, x86 Family 15 Model 2 Stepping 7 GenuiniteIntel ~2790
Mhz, no hyperthreading
No Write cache
One core per cpu
drives: 1 36gb scsi 1 72gbscsi (I'm running on the 62gb drive).
Linux:
Suse 9.1 (I know, oldish).
2 cpus - Intel(R) Pentium(R) 4 CPU 3.00GHz, no hyperthreading
No write Cache, one core per cpu
dual boot, with 28G disk space to linux.
java: Java(TM) SE Runtime Environment (build pxi3260sr3-20081007_01(SR3))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260-20081001_2388
3 (JIT enabled, AOT enabled)
J9VM - 20081001_023883_lHdSMr
JIT - r9_20080930_1330
GC - 20080926_AA)
JCL - 20080924_01
I've used the same nightly build: version: 10.5.0.0 alpha - (745360)
My next step is to run on the linux box with just the
derby.stream.error.logSeverityLevel=0
derby.language.logStatementText=true
in derby.properties, and on the linux box with the interrupts happening more
often.
For now, looks like we're no closer to figuring out what's going on with this.
> 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, derbylog.zip,
> performance.out
>
>
> 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.readertoutf8str...@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.
