db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3643) store/bootLock.java fails on AIX with ibm16
Date Fri, 25 Apr 2008 20:05:55 GMT

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


Mime
View raw message