ERROR Cannot configure jgroups 'kubernetes.KUBE_PING' protocol under 'tcp' stack. This protocol is already configured.

Latest response

I am unable to restart a stopped JBoss EAP 7.3 with OpenJDK11 Docker image1.

Steps to reproduce:

  1. Create and start a new container:

docker run -d --name jboss-eap-73 -p 18080:8080 -e DISABLE_EMBEDDED_JMS_BROKER=true registry.redhat.io/jboss-eap-7/eap73-openjdk11-openshift-rhel8

  1. Stop the running container:

docker stop jboss-eap-73

  1. Restart the stopped container:

docker start jboss-eap-73

Expected behaviour:

  • The container can be restarted successfully

Actual behaviour:

  • The container cannot be restarted because of the following error:

Error applying /tmp/cli-configuration-script-1595581623.cli CLI script. Embedded server started successfully. The Operations were executed but there were unexpected values. See list of errors in /tmp/cli-script-error-1595581623.cli
ERROR Cannot configure jgroups 'kubernetes.KUBE_PING' protocol under 'tcp' stack. This protocol is already configured.

Is there any known solution for this problem?

Thanks

DP
Log in to join the conversation

Responses

RZ Newbie 5 points
5 August 2020 9:10 AM

I have the same problem using JBoss EAP 7.3 with OpenJDK8 image (jboss-eap-7/eap73-openjdk8-openshift-rhel7)

JR Newbie 5 points
25 August 2020 8:20 AM

I had this message as well. What worked for me was removed the two instances of 'protocol type="kubernetes.KUBE_PING' from standalone-openshift.xml

AA Newbie 7 points
10 September 2020 11:50 PM

Same problem.... This is all because of lack of documentation for these images to be honest, I searched everywhere and did not find a list of the config params for this image

wc Newbie 5 points
8 April 2021 9:50 AM

I have the same problem....

IS Community Member 56 points
6 December 2021 10:59 AM

Same problem with registry.redhat.io/jboss-eap-7/eap74-openjdk11-openshift-rhel8:7.4.2-4

CC Newbie 10 points
28 January 2022 10:01 AM

Same problem with registry.redhat.io/jboss-eap-7/eap74-openjdk8-openshift-rhel8:7.4.2

FC Newbie 5 points
20 February 2023 3:46 PM

Same problem with registry.redhat.io/jboss-eap-7/eap74-openjdk8-openshift-rhel7:7.4.9-4

I figured out the problem, it's linked to the file "jgroups_common.sh" under the folder "/opt/eap/bin/launch/". The method "configure_protocol_cli_helper" generates CLI commands that are executed at runtime. I don't understand why this helper add this block:

if (outcome == success) of /subsystem=jgroups/stack="${stack}"/protocol="${protocol}":read-resource echo Cannot configure jgroups '${protocol}' protocol under '${stack}' stack. This protocol is already configured. >> \${error_file} quit end-if

The "echo" is not allowed to be executed... and the "quit" neither! The solution (workaround) is to remove these lines in your custom image. Personally I used a sed command to do that:

"sed -i '/echo Cannot configure jgroups|quit/d' /opt/eap/bin/launch/jgroups_common.sh"

Now the container can be restart without errors. I hope it will be fixed in future release...