activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-2738) KahaDB lock timeout should be configurable.
Date Wed, 16 Jun 2010 10:20:52 GMT

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

Rob Davies resolved AMQ-2738.
-----------------------------

    Resolution: Fixed

Fixed by SVN revision 955179 - added property databaseLockedWaitDelay on to KahaDBPersistenceAdapter
with a default of 10000 ms

> 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: Rob Davies
>             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.


Mime
View raw message