You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/09 15:01:00 UTC
[jira] [Commented] (ARTEMIS-1788) JDBC HA should use JDBC Network
Timeout
[ https://issues.apache.org/jira/browse/ARTEMIS-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16430647#comment-16430647 ]
ASF GitHub Bot commented on ARTEMIS-1788:
-----------------------------------------
GitHub user franz1981 opened a pull request:
https://github.com/apache/activemq-artemis/pull/2003
ARTEMIS-1788 JDBC HA should use JDBC Network Timeout
JdbcNodeManager is configured to use the same network timeout
value of the journal and to validate all the timeout values
related to a correct HA behaviour.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/franz1981/activemq-artemis ARTEMIS-1788
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/2003.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 #2003
----
commit a8917316e8eb497f1738b77415d0f8523351cbfe
Author: Francesco Nigro <ni...@...>
Date: 2018-04-09T14:26:37Z
ARTEMIS-1788 JDBC HA should use JDBC Network Timeout
JdbcNodeManager is configured to use the same network timeout
value of the journal and to validate all the timeout values
related to a correct HA behaviour.
----
> JDBC HA should use JDBC Network Timeout
> ---------------------------------------
>
> Key: ARTEMIS-1788
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1788
> 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 JDBC Node Manager doesn't use the JDBC Network Timeout used on the rest of the Journal.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)