[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] Updated: (AMQ-2738) KahaDB lock timeout should be
From:       "Gary Tully (JIRA)" <jira () apache ! org>
Date:       2010-05-27 16:51:52
Message-ID: 11043560.4941274979112139.JavaMail.jira () thor
[Download RAW message or body]


     [ https://issues.apache.org/activemq/browse/AMQ-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Gary Tully updated AMQ-2738:
----------------------------

         Assignee: Gary Tully
    Fix Version/s: 5.4.0
      Component/s: Broker

> KahaDB lock timeout should be configurable.
> -------------------------------------------
> 
> Key: AMQ-2738
> URL: https://issues.apache.org/activemq/browse/AMQ-2738
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.2
> Reporter: Adrian Trenaman
> Assignee: Gary Tully
> Fix For: 5.4.0
> 
> 
> The timeout for KahaDB acquiring a lock on the file store is 10seconds - surely \
> this should be configurable! The AMQ Persistence Adaptor store was pretty much \
> immediate in it's take up on failover from master to slave; with the hard-coded 10 \
> second delay in KahaDB it can take too long to failover. Thoughts? 

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


[prev in list] [next in list] [prev in thread] [next in thread]