db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (DERBY-4179) bootLock.java fails with missing exception on z/OS with pmz3160sr2ifix-20081021_01(SR2+IZ32776+IZ33456), and Windows Vista
Date Fri, 07 May 2010 16:59:47 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865235#action_12865235
] 

Dag H. Wanvik edited comment on DERBY-4179 at 5/7/10 12:57 PM:
---------------------------------------------------------------

Uploading version 4 of this test, please review.
Passes for me on Windows, Sun phoneME and Solaris/Linux.
Rerunning regressions now.

Details:

* Rewrite of boot lock test to JUnit.

* Added test of effectiveness of derby.database.forceDatabaseLock for
  phoneME platforms, until we implement DERBY-4646. (I could not find
  any other such test).

* Fixed JUnit harness to correctly fork a Sun phoneME vm (image name
  is cvm, not java),

* Added logic to capture what happens to minion (if it fails) by
  capturing its stderr (if it ever gets started, that is), cf. example enclosed.

* Added socket logic to communicate to parent when minion has booted
  the "dual boot" candidate to avoid having to wait for 30 seconds or
  more to be sure it has done so. Test now runs in a new seconds.

* Skips test for j9 for now, since this platform fails on the fork
  operation according to Kathey. I suggest we open a new JIRA to fix
  this if desired.


Example of the minion failing:
-----------------------------
There was 1 failure:
1) testBootLock(org.apache.derbyTesting.functionTests.tests.store.BootLockTest)junit.framework.AssertionFailedError:
Minion did not start or boot db in 60 seconds.
----Minion's stderr:
java.lang.Exception: Stack trace	at java.lang.Thread.dumpStack(Thread.java:1206)	at org.apache.derbyTesting.functionTests.tests.store.BootLockMinion.main(BootLockMinion.java:48)
----Minion's stderr ended
	at org.apache.derbyTesting.functionTests.tests.store.BootLockTest.testBootLock(BootLockTest.java:201)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
	at junit.extensions.TestSetup.run(TestSetup.java:25)
	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
	at junit.extensions.TestSetup.run(TestSetup.java:25)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
	at junit.extensions.TestSetup.run(TestSetup.java:25)

FAILURES!!!
Tests run: 1,  Failures: 1,  Errors: 0


      was (Author: dagw):
    Uploading version 4 of this test, please review.
Passes for me on Windows, Sun phoneME and Solaris/Linux.
Rerunning regressions now.

Details:

* Rewrite of boot lock test to JUnit.

* Added test of effectiveness of derby.database.forceDatabaseLock for
  phoneME platforms, until we implement DERBY-4646. (I could not find
  any other such test).

* Fixed JUnit harness to correctly fork a Sun phoneME vm (image name
  is cvm, not java),

* Added logic to capture what happens to minion if ist fails by
  capturing its stderr (if it ever gets started, that is), cf. example enclosed.

* Added socket logic to communicate to parent when minion has booted
  the "dual boot" candidate to avoid having to wait for 30 seconds or
  more to be sure it has done so. Test now runs in a new seconds.

* Skips test for j9 for now, since this platform fails on the fork
  operation according to Kathey. I suggest we open a new JIRA to fix
  this of desired.


Example of the minion failing:
-----------------------------
There was 1 failure:
1) testBootLock(org.apache.derbyTesting.functionTests.tests.store.BootLockTest)junit.framework.AssertionFailedError:
Minion did not start or boot db in 60 seconds.
----Minion's stderr:
java.lang.Exception: Stack trace	at java.lang.Thread.dumpStack(Thread.java:1206)	at org.apache.derbyTesting.functionTests.tests.store.BootLockMinion.main(BootLockMinion.java:48)
----Minion's stderr ended
	at org.apache.derbyTesting.functionTests.tests.store.BootLockTest.testBootLock(BootLockTest.java:201)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
	at junit.extensions.TestSetup.run(TestSetup.java:25)
	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
	at junit.extensions.TestSetup.run(TestSetup.java:25)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
	at junit.extensions.TestSetup.run(TestSetup.java:25)

FAILURES!!!
Tests run: 1,  Failures: 1,  Errors: 0

  
> bootLock.java fails with missing exception on z/OS with  pmz3160sr2ifix-20081021_01(SR2+IZ32776+IZ33456),
and Windows Vista
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4179
>                 URL: https://issues.apache.org/jira/browse/DERBY-4179
>             Project: Derby
>          Issue Type: Bug
>          Components: Store, Test
>    Affects Versions: 10.5.1.1
>         Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pmz3160sr2ifix-20081021_01(SR2+IZ32776+IZ33456))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 z/OS s390-31 jvmmz3160ifx-20081010_24288
(JIT enabled, AOT enabled)
> J9VM - 20081009_024288_bHdSMr
> JIT  - r9_20080721_1330ifx2
> GC   - 20080724_AA)
> JCL  - 20080808_02
> ------------------------------------------
> Also seen on : Vista Ultimate 32 bits under cygwin with Sun JRE 1.6.0_07-b06
>            Reporter: Kathey Marsden
>            Assignee: Dag H. Wanvik
>         Attachments: bootLock.diff, derby-4179-junit-2.diff, derby-4179-junit-2.stat,
derby-4179-junit-3.diff, derby-4179-junit-3.stat, derby-4179-junit-4.diff, derby-4179-junit-4.stat,
derby-4179-junit.diff, derby-4179-junit.stat, derby-4179.diff, derby-4179.stat, derbyall_report.txt,
storeall_report.txt, sysinfo.txt
>
>
> I saw this diff in store/bootLock.java. I did not see it with the 64bit jvm run on 10.5.1.0
RC1
> *** Start: bootLock jdk1.6.0 storeall:storemore 2009-04-21 19:10:18 ***
> 2,4d1
> < expected exception
> < SQLSTATE(XJ040):
> < SQLSTATE(XSDB6):
> Test Failed.
> *** End:   bootLock jdk1.6.0 storeall:storemore 2009-04-21 19:11:00 ***
> The test passed on rerun when run independently.

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