-
Bug
-
Resolution: Done
-
Blocker
-
AMQ 7.9.1.GA
-
False
-
False
-
When executing AMQ Broker Operator 7.8, the startup of the Broker took 39 seconds which leads to crash loop back. We did see in the pod log:
2021-11-28 12:25:07,014 WARNING [org.jgroups.stack.Configurator] JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead 2021-11-28 12:25:07,305 INFO [org.jgroups.protocols.openshift.DNS_PING] serviceName [ex-aao-ping-svc] set; clustering enabled 2021-11-28 12:25:46,346 INFO [org.openshift.ping.common.Utils] 3 attempt(s) with a 1000ms sleep to execute [GetServicePort] failed. Last failure was [javax.naming.CommunicationException: DNS error] 2021-11-28 12:25:46,347 WARNING [org.jgroups.protocols.openshift.DNS_PING] No DNS SRV record found for service [ex-aao-ping-svc]
NOTE: For 7.10 the jgroups was upgraded in the distro from v3 to v5 and the way in which the dns was used within openshift by jgroups changed. This was reconfigured and retested during development to ensure broker clustering worked OK.
ACTION: For 7.10. we want to be sure that this same situation cannot occur with the new configuration for jgroups v5 with the integrated DNS.
