Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: None
Affects Version/s: AMQ 7.9.1.GA
Component/s: broker-core, container image
Labels:
- broker
- dns

Blocked:
False
Ready:
False
Target Release:

AMQ 7.8.4.OPR.1.GA

SFDC Cases Counter:
SFDC Cases Links:

Description

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]

Attachments

Issue Links

is cloned by

ENTMQBR-6547 AMQ broker pod [7.8] took 39 seconds to start due to a DNS error "No DNS SRV record found for service"

Closed

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(4 mentioned in)

Activity

People

Assignee:: Howard Gao

Reporter:: Abel Bouchama

Tester:: Mikhail Krutov

Votes:: 1 Vote for this issue

Watchers:: 9 Start watching this issue

Dates

Created:: 2021/11/30 1:48 PM

Updated:: 2022/04/12 12:19 PM

Resolved:: 2022/01/31 4:21 PM