[
https://issues.apache.org/jira/browse/ARTEMIS-2637?focusedWorklogId=394940&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-394940
]
ASF GitHub Bot logged work on ARTEMIS-2637:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Feb/20 15:21
Start Date: 28/Feb/20 15:21
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on issue #2994: ARTEMIS-2637
Making UDP client discovery resilient
URL: https://github.com/apache/activemq-artemis/pull/2994#issuecomment-592560292
there's a test failure on the main testsuite (the one that takes 2 hours).
and I'm adding some checks around serialization.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 394940)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
