You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2018/05/17 02:36:10 UTC

[jira] [Reopened] (ARTEMIS-1767) JDBC Lock Acquisition Timeout should behave like the file based version

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

clebert suconic reopened ARTEMIS-1767:
--------------------------------------

> JDBC Lock Acquisition Timeout should behave like the file based version
> -----------------------------------------------------------------------
>
>                 Key: ARTEMIS-1767
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1767
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.5.0
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Major
>             Fix For: 2.6.0
>
>
> The journal lock timeout (file-based) is infinite by default, not customizable by the user's configuration and exposed programmatically just for testing purposes: the JDBC version of it need to do the same in order to avoid being misconfigured, breaking JDBC HA reliability.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)