[
https://issues.apache.org/jira/browse/ARTEMIS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410026#comment-16410026
]
ASF GitHub Bot commented on ARTEMIS-1767:
-----------------------------------------
GitHub user franz1981 opened a pull request:
https://github.com/apache/activemq-artemis/pull/1972
ARTEMIS-1767 JDBC Lock Acquisition Timeout should behave like the file
based version
The JDBC Lock Acquisition Timeout is no longer exposed to any user
configuration and defaulted to infinite to match the behaviour of the journal
(file-based) one.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/franz1981/activemq-artemis
no_jdbc_lock_acq_timeout
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1972.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1972
----
commit 6e9ce27a6e36454dafa3749139ae96d45f34b380
Author: Francesco Nigro <nigro.fra@...>
Date: 2018-03-22T18:13:49Z
ARTEMIS-1767 JDBC Lock Acquisition Timeout should behave like the file
based version
The JDBC Lock Acquisition Timeout is no longer exposed to any user
configuration and defaulted to infinite to match the behaviour of the journal
(file-based) one.
----
> 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)
