activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dudaerich <...@git.apache.org>
Subject [GitHub] activemq-artemis issue #1318: ARTEMIS-1208 Do not use reconnect-atempts=-1 i...
Date Wed, 07 Jun 2017 06:55:45 GMT
Github user dudaerich commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1318
  
    @clebertsuconic Yes, I did. Currently there is a known issue with replicated HA and the
number of failed tests in this area differs with each run. It is hard to say if this commit
breaks some tests or not. I took a brief look on test results but I didn't identify any failure
caused by some kind of error that connection was closed or something like that. All issues
what I saw where related to either set up phase (backup wasn't synchronized with live in timeout)
or clients didn't receive response on packet.
    
    To be 100% sure we can increase reconnect-attempts or reconnect-delay. Currently reconnect-delay=50
and reconnect-attempts=200 what gives clients 10s to reconnect. Maybe we can increase the
time to 30s. E.g. reconnect-delay=100 and reconnect-attempts=300 wdyt?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message