[AMQ Broker] AMQ Broker pod slow to start with a WARN "No DNS SRV record found for service"
Issue
-
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]
-
AMQ Broker shows the following log when started:
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]
Environment
- OpenShift Container 4
- AMQ Broker: 7.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.