[jira] Reopened: (DERBY-1003) store/bootLock.java fails with J2ME/CDC/FP

["Manjula Kutty (JIRA)" <ji...@apache.org>]

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

Manjula Kutty reopened DERBY-1003:
----------------------------------


This one occured again on 10.4 with weme6.1.
*** Start: bootLock jdkJ2ME Foundation Specification v1.1 storeall:storemore 2008-04-17 11:18:06 ***
2 del
< expected exception
3 del
< SQLSTATE(XJ040): 
4 del
< SQLSTATE(XSDB6): 
4a2,3
> FAIL -- unexpected exception: java.io.IOException: Unable to start program
> java.io.IOException: Unable to start program

> store/bootLock.java fails with J2ME/CDC/FP
> ------------------------------------------
>
>                 Key: DERBY-1003
>                 URL: https://issues.apache.org/jira/browse/DERBY-1003
>             Project: Derby
>          Issue Type: Test
>          Components: Regression Test Failure
>    Affects Versions: 10.2.1.6
>         Environment: IBM WCTME 5.7 j9_foundation
>            Reporter: Deepa Remesh
>
> store/bootLock.java failed with j9_foundation VM in the weekend run. I ran this test few times on my machine and the test does not fail. Also, there was no exception in the weekend run failure. It seems like the second jvm which is started to boot Derby did not start in time.
> What test does: 
> The test starts a second jvm (by calling store/bootLock1.java) which boots Derby. The test sleeps for some time waiting for the second jvm to start and boot Derby. Then it tries to boot Derby again and should get an expected exception for double-booting. From the failure, it seems like this second jvm did not start at all. I am guessing this could be a timing issue. I'll check if the test fails this weekend too.
> If anyone else sees this test fail with j9_foundation VM and has more information, please update this JIRA.

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