[
https://issues.apache.org/jira/browse/ARTEMIS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417604#comment-16417604
]
ASF subversion and git services commented on ARTEMIS-1767:
----------------------------------------------------------
Commit a9cfc08e6727bb3f3a628e0dabf4725cb23be753 in activemq-artemis's branch
refs/heads/1.x from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=a9cfc08 ]
ARTEMIS-1767 JDBC Lock Acquisition Timeout should behave like the file based
version
(cherry picked from commit 6e9ce27a6e36454dafa3749139ae96d45f34b380)
> 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.5.1
>
>
> 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)
