[
https://issues.apache.org/jira/browse/ARTEMIS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047925#comment-17047925
]
ASF subversion and git services commented on ARTEMIS-2637:
----------------------------------------------------------
Commit ea3c592c82958d12b8f7115195076be0fefee428 in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ea3c592 ]
ARTEMIS-2637 Adding additional logging and fixing checkstyle
> 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: 1h 10m
> 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)
