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 "Deepa Remesh (JIRA)" <de...@db.apache.org> on 2006/02/17 21:06:24 UTC
[jira] Created: (DERBY-1003) store/bootLock.java fails with
J2ME/CDC/FP
store/bootLock.java fails with J2ME/CDC/FP
------------------------------------------
Key: DERBY-1003
URL: http://issues.apache.org/jira/browse/DERBY-1003
Project: Derby
Type: Test
Versions: 10.2.0.0
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1003) store/bootLock.java fails with
J2ME/CDC/FP
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1003?page=all ]
Mike Matrigali updated DERBY-1003:
----------------------------------
Component: Regression Test Failure
> store/bootLock.java fails with J2ME/CDC/FP
> ------------------------------------------
>
> Key: DERBY-1003
> URL: http://issues.apache.org/jira/browse/DERBY-1003
> Project: Derby
> Type: Test
> Components: Regression Test Failure
> Versions: 10.2.0.0
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Reopened: (DERBY-1003) store/bootLock.java fails with
J2ME/CDC/FP
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reopened DERBY-1003:
-----------------------------------
I saw this on the Friday 5/9/2008 run in the IBM test runs.
For some reason this night's run did not show up on the public website.
*** Start: bootLock jdkJ2ME Foundation Specification v1.1 storeall:storemore 2008-05-10 01:38:27 ***
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.
[jira] Commented: (DERBY-1003) store/bootLock.java fails with
J2ME/CDC/FP
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596109#action_12596109 ]
Kathey Marsden commented on DERBY-1003:
---------------------------------------
This failiure was on the new machine setup for 10.4, so might be an environment issue.
> 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.
[jira] Closed: (DERBY-1003) store/bootLock.java fails with
J2ME/CDC/FP
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1003?page=all ]
Deepa Remesh closed DERBY-1003:
-------------------------------
Resolution: Cannot Reproduce
This issue seemed to be a test timing problem and does not occur any more.
> store/bootLock.java fails with J2ME/CDC/FP
> ------------------------------------------
>
> Key: DERBY-1003
> URL: http://issues.apache.org/jira/browse/DERBY-1003
> Project: Derby
> Type: Test
> Components: Regression Test Failure
> Versions: 10.2.0.0
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-1003) store/bootLock.java fails with
J2ME/CDC/FP
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-1003.
-------------------------------------
Resolution: Invalid
This time I'm closing this as invalid - it's a setup issue with this specific jvm.
> 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.
[jira] Reopened: (DERBY-1003) store/bootLock.java fails with
J2ME/CDC/FP
Posted by "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.
[jira] Closed: (DERBY-1003) store/bootLock.java fails with
J2ME/CDC/FP
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-1003.
-------------------------------------
Resolution: Cannot Reproduce
The recent report is not a re-occurrence; it is undoubtedly a problem with the setup. That error is always issued by this jvm when something in the setup is amiss; the original problem did not report this error and was thus something else.
I ran the test on my machine and it passes fine; the setup issues should be dealt with separately; I suggest checking path settings including bootclasspath and other values passed in to the jvm.
Setting back to original closing value.
> 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.