Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.3.x
Affects Version/s: 7.3.4.GA
Component/s: Documentation, OpenShift
Labels:
None

Story Points:
5
Blocked:
False
Ready:
False
Affects:

Release Notes
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Release Note Text:
OPENSHIFT_DNS_PING_SERVICE_NAME now may not be set to an empty value, and doing so will result in a boot error, disabling clustering.
Target Release:

7.3.z.GA
Git Pull Request:
https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-for-openshift/-/merge_requests/521
Steps to Reproduce:
Hide

1. create new app.

$ oc new-project eap-demo $ oc new-app --template=eap73-openjdk11-basic-s2i \ -p APPLICATION_NAME="helloworld" \ -p IMAGE_STREAM_NAMESPACE=eap-demo \ -p SOURCE_REPOSITORY_URL=https://github.com/jboss-developer/jboss-eap-quickstarts \ -p SOURCE_REPOSITORY_REF=7.3.x-openshift \ -p CONTEXT_DIR=helloworld

2. After started, change the OPENSHIFT_DNS_PING_SERVICE_NAME's value to empty.

$ oc set env pod/<podname> --list OPENSHIFT_DNS_PING_SERVICE_NAME=helloworld-ping ... $ oc edit dc/helloworld -o yaml 43 spec: 44 containers: 45 - env: 46 - name: JGROUPS_PING_PROTOCOL 47 value: dns.DNS_PING 48 - name: OPENSHIFT_DNS_PING_SERVICE_NAME 49 value: helloworld-ping // delete value $ oc set env pod/<podname> --list OPENSHIFT_DNS_PING_SERVICE_NAME=

3. After restarting the pod, the error can be seen on the log.

$ oc logs <new podname>
Show
1. create new app. $ oc new -project eap-demo $ oc new -app --template=eap73-openjdk11-basic-s2i \ -p APPLICATION_NAME= "helloworld" \ -p IMAGE_STREAM_NAMESPACE=eap-demo \ -p SOURCE_REPOSITORY_URL=https: //github.com/jboss-developer/jboss-eap-quickstarts \ -p SOURCE_REPOSITORY_REF=7.3.x-openshift \ -p CONTEXT_DIR=helloworld 2. After started, change the OPENSHIFT_DNS_PING_SERVICE_NAME's value to empty. $ oc set env pod/<podname> --list OPENSHIFT_DNS_PING_SERVICE_NAME=helloworld-ping ... $ oc edit dc/helloworld -o yaml 43 spec: 44 containers: 45 - env: 46 - name: JGROUPS_PING_PROTOCOL 47 value: dns.DNS_PING 48 - name: OPENSHIFT_DNS_PING_SERVICE_NAME 49 value: helloworld-ping // delete value $ oc set env pod/<podname> --list OPENSHIFT_DNS_PING_SERVICE_NAME= 3. After restarting the pod, the error can be seen on the log. $ oc logs < new podname>
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

According to the document [1], the server will start as a single-node cluster when OPENSHIFT_DNS_PING_SERVICE_NAME is set empty.
But the server fails to start with following error [2].

[1]

The OPENSHIFT_DNS_PING_SERVICE_NAME environment variable must be set to the name of the ping service for the cluster. If not set, the server will act as if it is a single-node cluster (a "cluster of one").

https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.3/html/getting_started_with_jboss_eap_for_openshift_online/reference_information#configuring_a_jgroups_discovery_mechanism

[2]

 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 80) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalStateException: java.lang.IllegalArgumentException: dns_query can not be null or empty
	at org.wildfly.clustering.service@7.3.4.GA-redhat-00003//org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:70)
	at org.wildfly.clustering.service@7.3.4.GA-redhat-00003//org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117)
	at org.jboss.threads@2.3.3.Final-redhat-00001//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads@2.3.3.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
	at org.jboss.threads@2.3.3.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
	at org.jboss.threads@2.3.3.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
	at java.base/java.lang.Thread.run(Thread.java:834)
	at org.jboss.threads@2.3.3.Final-redhat-00001//org.jboss.threads.JBossThread.run(JBossThread.java:485)
Caused by: java.lang.IllegalStateException: java.lang.IllegalArgumentException: dns_query can not be null or empty
	at org.jboss.as.clustering.jgroups@7.3.4.GA-redhat-00003//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116)
	at org.jboss.as.clustering.jgroups@7.3.4.GA-redhat-00003//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58)
	at org.wildfly.clustering.service@7.3.4.GA-redhat-00003//org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67)
	... 7 more
Caused by: java.lang.IllegalArgumentException: dns_query can not be null or empty
	at org.jgroups@4.1.10.Final-redhat-00001//org.jgroups.protocols.dns.DNS_PING.validateProperties(DNS_PING.java:64)
	at org.jgroups@4.1.10.Final-redhat-00001//org.jgroups.protocols.dns.DNS_PING.init(DNS_PING.java:50)
	at org.jgroups@4.1.10.Final-redhat-00001//org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:841)
	at org.jgroups@4.1.10.Final-redhat-00001//org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:829)
	at org.jgroups@4.1.10.Final-redhat-00001//org.jgroups.JChannel.<init>(JChannel.java:155)
	at org.jboss.as.clustering.jgroups@7.3.4.GA-redhat-00003//org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:116)
	at org.jboss.as.clustering.jgroups@7.3.4.GA-redhat-00003//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:96)
	... 9 more

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

console.log
24 kB
2021/01/07 5:28 AM
deploymentconfig.yaml
4 kB
2021/01/07 5:31 AM
standalone-openshift.xml
36 kB
2021/01/07 5:30 AM

is cloned by

CLOUD-3890 "IllegalArgumentException: dns_query can not be null or empty" when OPENSHIFT_DNS_PING_SERVICE_NAME set empty

Verified

JBEAP-22948 [7.4.z] "IllegalArgumentException: dns_query can not be null or empty" when OPENSHIFT_DNS_PING_SERVICE_NAME set empty

Closed

Assignee:: Gaurav Trivedi

Reporter:: Hiroki Daicho (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 12 Start watching this issue

Created:: 2021/01/07 5:26 AM

Updated:: 2024/08/27 1:43 PM

Resolved:: 2021/12/21 6:41 AM

Details

Description

Attachments

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates