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 "Manjula Kutty (JIRA)" <ji...@apache.org> on 2008/04/24 21:33:25 UTC
[jira] Created: (DERBY-3643) store/bootLock.java fails on AIX with
ibm16yes
store/bootLock.java fails on AIX with ibm16yes
----------------------------------------------
Key: DERBY-3643
URL: https://issues.apache.org/jira/browse/DERBY-3643
Project: Derby
Issue Type: Bug
Reporter: Manjula Kutty
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3643) store/bootLock.java fails on AIX
with ibm16
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592497#action_12592497 ]
Kathey Marsden commented on DERBY-3643:
---------------------------------------
Thanks Manjula.
I will file a jvm bug.
Kathey
> store/bootLock.java fails on AIX with ibm16
> -------------------------------------------
>
> Key: DERBY-3643
> URL: https://issues.apache.org/jira/browse/DERBY-3643
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.4.1.3
> Environment: OS : AIX 5.3
> Java : $ java -version
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pap3260-20071123_01)
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32 jvmap3260-20071121_15015
> (JIT enabled)
> J9VM - 20071121_015015_bHdSMR
> JIT - r9_20071121_1330
> GC - 20071031_AA)
> JCL - 20071118_01
> Reporter: Manjula Kutty
> Attachments: TestExclusiveLock.java
>
>
> Here is the diff:
> Framework: embedded
> *** Start: bootLock jdk1.6.0 2008-04-24 11:27:51 ***
> 2 del
> < expected exception
> 3 del
> < SQLSTATE(XJ040):
> 4 del
> < SQLSTATE(XSDB6):
> 4a2
> > WARNING: Derby (instance xxxxFILTERED-UUIDxxxx) is attempting to boot the data
> base /local1/mkutty/10.4/bootLock/wombat even though Derby (instance xxxxFILTERE
> D-UUIDxxxx) may still be active. Only one instance of Derby should boot a datab
> ase at a time. Severe and non-recoverable corruption can result and may have alr
> eady occurred.
> No other warnings or Exception in the derby.log
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3643) store/bootLock.java fails on AIX with
ibm16yes
Posted by "Manjula Kutty (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjula Kutty updated DERBY-3643:
---------------------------------
Description:
Here is the diff:
Framework: embedded
*** Start: bootLock jdk1.6.0 2008-04-24 11:27:51 ***
2 del
< expected exception
3 del
< SQLSTATE(XJ040):
4 del
< SQLSTATE(XSDB6):
4a2
> WARNING: Derby (instance xxxxFILTERED-UUIDxxxx) is attempting to boot the data
base /local1/mkutty/10.4/bootLock/wombat even though Derby (instance xxxxFILTERE
D-UUIDxxxx) may still be active. Only one instance of Derby should boot a datab
ase at a time. Severe and non-recoverable corruption can result and may have alr
eady occurred.
No other warnings or Exception in the derby.log
Environment:
OS : AIX 5.3
Java : $ java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap3260-20071123_01)
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32 jvmap3260-20071121_15015
(JIT enabled)
J9VM - 20071121_015015_bHdSMR
JIT - r9_20071121_1330
GC - 20071031_AA)
JCL - 20071118_01
Affects Version/s: 10.4.1.3
> store/bootLock.java fails on AIX with ibm16yes
> ----------------------------------------------
>
> Key: DERBY-3643
> URL: https://issues.apache.org/jira/browse/DERBY-3643
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.4.1.3
> Environment: OS : AIX 5.3
> Java : $ java -version
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pap3260-20071123_01)
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32 jvmap3260-20071121_15015
> (JIT enabled)
> J9VM - 20071121_015015_bHdSMR
> JIT - r9_20071121_1330
> GC - 20071031_AA)
> JCL - 20071118_01
> Reporter: Manjula Kutty
>
> Here is the diff:
> Framework: embedded
> *** Start: bootLock jdk1.6.0 2008-04-24 11:27:51 ***
> 2 del
> < expected exception
> 3 del
> < SQLSTATE(XJ040):
> 4 del
> < SQLSTATE(XSDB6):
> 4a2
> > WARNING: Derby (instance xxxxFILTERED-UUIDxxxx) is attempting to boot the data
> base /local1/mkutty/10.4/bootLock/wombat even though Derby (instance xxxxFILTERE
> D-UUIDxxxx) may still be active. Only one instance of Derby should boot a datab
> ase at a time. Severe and non-recoverable corruption can result and may have alr
> eady occurred.
> No other warnings or Exception in the derby.log
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3643) store/bootLock.java fails on AIX with
ibm16
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3643:
----------------------------------
Attachment: TestExclusiveLock.java
Hi Manjula,
Can you try this program TestExclusiveLock.java on your aix machine with the jvm causing the problem.
Run it once and you should see :
EXCLUSIVE_FILE_LOCK
Strike any key to exit
Don't strike a key to exit.
Then in a new window (same directory) run it again. You should see
EXCLUSIVE_FILE_LOCK_NOT_AVAILABLE
Strike any key to exit
That is at least how things should work if everything is working properly with the JVM. If the second run shows you got the EXCLUSIVE lock we are looking at a JVM bug.
Kathey
> store/bootLock.java fails on AIX with ibm16
> -------------------------------------------
>
> Key: DERBY-3643
> URL: https://issues.apache.org/jira/browse/DERBY-3643
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.4.1.3
> Environment: OS : AIX 5.3
> Java : $ java -version
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pap3260-20071123_01)
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32 jvmap3260-20071121_15015
> (JIT enabled)
> J9VM - 20071121_015015_bHdSMR
> JIT - r9_20071121_1330
> GC - 20071031_AA)
> JCL - 20071118_01
> Reporter: Manjula Kutty
> Attachments: TestExclusiveLock.java
>
>
> Here is the diff:
> Framework: embedded
> *** Start: bootLock jdk1.6.0 2008-04-24 11:27:51 ***
> 2 del
> < expected exception
> 3 del
> < SQLSTATE(XJ040):
> 4 del
> < SQLSTATE(XSDB6):
> 4a2
> > WARNING: Derby (instance xxxxFILTERED-UUIDxxxx) is attempting to boot the data
> base /local1/mkutty/10.4/bootLock/wombat even though Derby (instance xxxxFILTERE
> D-UUIDxxxx) may still be active. Only one instance of Derby should boot a datab
> ase at a time. Severe and non-recoverable corruption can result and may have alr
> eady occurred.
> No other warnings or Exception in the derby.log
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3643) store/bootLock.java fails on AIX
with ibm16
Posted by "Manjula Kutty (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592492#action_12592492 ]
Manjula Kutty commented on DERBY-3643:
--------------------------------------
I got the following Exception instead of EXCLUSIVE_FILE_LOCK_NOT_AVAILABLE
Strike any key to exit
$ java TestExclusiveLock
Exception in thread "main" java.io.IOException: The file access permissions do n
ot allow the specified action.
at sun.nio.ch.FileChannelImpl.lock0(Native Method)
at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:886)
at java.nio.channels.FileChannel.tryLock(FileChannel.java:962)
at TestExclusiveLock.main(TestExclusiveLock.java:12)
$
> store/bootLock.java fails on AIX with ibm16
> -------------------------------------------
>
> Key: DERBY-3643
> URL: https://issues.apache.org/jira/browse/DERBY-3643
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.4.1.3
> Environment: OS : AIX 5.3
> Java : $ java -version
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pap3260-20071123_01)
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32 jvmap3260-20071121_15015
> (JIT enabled)
> J9VM - 20071121_015015_bHdSMR
> JIT - r9_20071121_1330
> GC - 20071031_AA)
> JCL - 20071118_01
> Reporter: Manjula Kutty
> Attachments: TestExclusiveLock.java
>
>
> Here is the diff:
> Framework: embedded
> *** Start: bootLock jdk1.6.0 2008-04-24 11:27:51 ***
> 2 del
> < expected exception
> 3 del
> < SQLSTATE(XJ040):
> 4 del
> < SQLSTATE(XSDB6):
> 4a2
> > WARNING: Derby (instance xxxxFILTERED-UUIDxxxx) is attempting to boot the data
> base /local1/mkutty/10.4/bootLock/wombat even though Derby (instance xxxxFILTERE
> D-UUIDxxxx) may still be active. Only one instance of Derby should boot a datab
> ase at a time. Severe and non-recoverable corruption can result and may have alr
> eady occurred.
> No other warnings or Exception in the derby.log
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3643) store/bootLock.java fails on AIX with
ibm16
Posted by "Manjula Kutty (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjula Kutty updated DERBY-3643:
---------------------------------
Summary: store/bootLock.java fails on AIX with ibm16 (was: store/bootLock.java fails on AIX with ibm16yes)
> store/bootLock.java fails on AIX with ibm16
> -------------------------------------------
>
> Key: DERBY-3643
> URL: https://issues.apache.org/jira/browse/DERBY-3643
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.4.1.3
> Environment: OS : AIX 5.3
> Java : $ java -version
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pap3260-20071123_01)
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32 jvmap3260-20071121_15015
> (JIT enabled)
> J9VM - 20071121_015015_bHdSMR
> JIT - r9_20071121_1330
> GC - 20071031_AA)
> JCL - 20071118_01
> Reporter: Manjula Kutty
>
> Here is the diff:
> Framework: embedded
> *** Start: bootLock jdk1.6.0 2008-04-24 11:27:51 ***
> 2 del
> < expected exception
> 3 del
> < SQLSTATE(XJ040):
> 4 del
> < SQLSTATE(XSDB6):
> 4a2
> > WARNING: Derby (instance xxxxFILTERED-UUIDxxxx) is attempting to boot the data
> base /local1/mkutty/10.4/bootLock/wombat even though Derby (instance xxxxFILTERE
> D-UUIDxxxx) may still be active. Only one instance of Derby should boot a datab
> ase at a time. Severe and non-recoverable corruption can result and may have alr
> eady occurred.
> No other warnings or Exception in the derby.log
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-3643) store/bootLock.java fails on AIX with
ibm16
Posted by "Manjula Kutty (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjula Kutty closed DERBY-3643.
--------------------------------
Resolution: Invalid
> store/bootLock.java fails on AIX with ibm16
> -------------------------------------------
>
> Key: DERBY-3643
> URL: https://issues.apache.org/jira/browse/DERBY-3643
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.4.1.3
> Environment: OS : AIX 5.3
> Java : $ java -version
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pap3260-20071123_01)
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32 jvmap3260-20071121_15015
> (JIT enabled)
> J9VM - 20071121_015015_bHdSMR
> JIT - r9_20071121_1330
> GC - 20071031_AA)
> JCL - 20071118_01
> Reporter: Manjula Kutty
> Attachments: TestExclusiveLock.java
>
>
> Here is the diff:
> Framework: embedded
> *** Start: bootLock jdk1.6.0 2008-04-24 11:27:51 ***
> 2 del
> < expected exception
> 3 del
> < SQLSTATE(XJ040):
> 4 del
> < SQLSTATE(XSDB6):
> 4a2
> > WARNING: Derby (instance xxxxFILTERED-UUIDxxxx) is attempting to boot the data
> base /local1/mkutty/10.4/bootLock/wombat even though Derby (instance xxxxFILTERE
> D-UUIDxxxx) may still be active. Only one instance of Derby should boot a datab
> ase at a time. Severe and non-recoverable corruption can result and may have alr
> eady occurred.
> No other warnings or Exception in the derby.log
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.