[
https://issues.apache.org/jira/browse/ARTEMIS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410228#comment-16410228
]
ASF subversion and git services commented on ARTEMIS-1767:
----------------------------------------------------------
Commit b775cb251ffef2aa0c1d3b3019b43738189d0956 in activemq-artemis's branch
refs/heads/master from [~nigro....@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=b775cb2 ]
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)
