[prev in list] [next in list] [prev in thread] [next in thread]
List: activemq-dev
Subject: [jira] [Created] (AMQ-3301) LockFile in-jvm check is not
From: "Arthur Naseef (JIRA)" <jira () apache ! org>
Date: 2011-04-29 17:47:03
Message-ID: 211835523.12112.1304099223683.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]
LockFile in-jvm check is not thread-safe
----------------------------------------
Key: AMQ-3301
URL: https://issues.apache.org/jira/browse/AMQ-3301
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.4.2
Reporter: Arthur Naseef
Priority: Minor
kahadb/src/main/java/org/apache/kahadb/util/LockFile.java adds in-JVM locking to \
Channel.tryLock() using system properties. However, there is time between the \
read-and-check for an existing lock and setting a new lock.
I found this problem while running multiple brokers in a single JVM for diagnostic \
purposes with two brokers using a shared directory to simlute a production H/A \
environment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic