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

Posted to dev@activemq.apache.org by franz1981 <gi...@git.apache.org> on 2018/03/22 18:14:48 UTC

[GitHub] activemq-artemis pull request #1972: ARTEMIS-1767 JDBC Lock Acquisition Time...

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

----


---

[GitHub] activemq-artemis pull request #1972: ARTEMIS-1767 JDBC Lock Acquisition Time...

Posted by asfgit <gi...@git.apache.org>.

Github user asfgit closed the pull request at:

    https://github.com/apache/activemq-artemis/pull/1972


---