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

Posted to issues@activemq.apache.org by "Howard Gao (Jira)" <ji...@apache.org> on 2020/03/04 00:21:00 UTC

[jira] [Commented] (ARTEMIS-2176) RA connection properties are not propagated to XARecoveryConfig

    [ https://issues.apache.org/jira/browse/ARTEMIS-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050659#comment-17050659 ] 

Howard Gao commented on ARTEMIS-2176:
-------------------------------------

The merged commit cb8da541107355f16eb26b21b6563a06876b741f as part of this fix has wrong JIRA number. i.e. the commit message:
commit cb8da541107355f16eb26b21b6563a06876b741f (spyrkob/ARTEMIS-2176, syprkob_ARTEMIS-2176_final)
Author: Howard Gao <ho...@gmail.com>
Date:   Tue Mar 3 18:48:18 2020 +0800

    ARTEMIS-*2716* Refactoring

Refers to a wrong JIRA number *2716* instead of *2176*.


> RA connection properties are not propagated to XARecoveryConfig
> ---------------------------------------------------------------
>
>                 Key: ARTEMIS-2176
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2176
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.6.3
>            Reporter: Bartosz Spyrko-Smietanko
>            Priority: Major
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> XARecoveryConfig#createServerLocator uses only TransportConfiguration/DiscoveryGroupConfiguration to create a new instance of ServerLocator. That means that connection properties like connectionTTL or callFailoverTime are ignored.  This can lead to network issues - eg. [https://issues.jboss.org/browse/WFLY-10725] 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)