[
https://issues.apache.org/jira/browse/ARTEMIS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047807#comment-17047807
]
ASF subversion and git services commented on ARTEMIS-2637:
----------------------------------------------------------
Commit 0cac669840d22ed6b9b89b5bdecc91f0c9d53126 in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=0cac669 ]
ARTEMIS-2637 Making UDP client discovery resilient
In case there is a hardware, firewal or any other thing making the UDP
connection to go deaf
we will now reopen the connection in an attempt to go over possible issues.
This is also improving locking around DiscoveryGroup initial connection.
> Resilience around UDP Discovery
> -------------------------------
>
> Key: ARTEMIS-2637
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2637
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.11.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.12.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> when Using the Client Discovery, if there is no response from the servers,
> the client fails with a timeout.
> I have been dealing with a situation where something drops the UDP
> connection, such as firewal, OS, I don't know what... but that required me to
> add a retry logic on that specific case.
> so, in case there's a timeout on the client and discovery is being used, the
> client will now reconnect UDP.
> and the initial-connect-attempts will also be used to loop around the
> discovery part.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
