You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Adrian Trenaman (JIRA)" <ji...@apache.org> on 2010/05/18 19:21:22 UTC

[jira] Created: (AMQ-2738) KahaDB lock timeout should be configurable.

KahaDB lock timeout should be configurable.
-------------------------------------------

                 Key: AMQ-2738
                 URL: https://issues.apache.org/activemq/browse/AMQ-2738
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.3.2
            Reporter: Adrian Trenaman


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.

[jira] Resolved: (AMQ-2738) KahaDB lock timeout should be configurable.

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ 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.

[jira] Updated: (AMQ-2738) KahaDB lock timeout should be configurable.

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
     [ 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.

[jira] Assigned: (AMQ-2738) KahaDB lock timeout should be configurable.

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies reassigned AMQ-2738:
-------------------------------

    Assignee: Rob Davies  (was: Gary Tully)

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