Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-2151

[EAP7] Scaling pod down causes ActiveMQ AMQ214016 NoRouteToHost error messages

    XMLWordPrintable

Details

    • Workaround Exists
    • Hide

      Get a copy of this standalone-openshift.xml and modify it commenting out the following lines:
      https://github.com/jboss-openshift/cct_module/blob/1.0/os-eap70-openshift/added/standalone-openshift.xml#L31

      https://github.com/jboss-openshift/cct_module/blob/1.0/os-eap70-openshift/added/standalone-openshift.xml#L344-L346

      Add the modified standalone-openshift.xml to the container build.
      Via S2I build:

      • Create a configuration directory in the top level of the pods git repository
      • Place the modified standalone-openshift.xml in the configuration directory
      • Rebuild the container and the modified XML will be copied into the container.

      Via Dockerfile build:

      • Add an instruction in the Dockerfile to copy the modified standalone-openshift.xml file into the container 
        COPY standalone-openshift.xml  /opt/eap/standalone/configuration
      • Rebuild the container and the modified XML will be copied into the container.
      Show
      Get a copy of this standalone-openshift.xml and modify it commenting out the following lines: https://github.com/jboss-openshift/cct_module/blob/1.0/os-eap70-openshift/added/standalone-openshift.xml#L31 https://github.com/jboss-openshift/cct_module/blob/1.0/os-eap70-openshift/added/standalone-openshift.xml#L344-L346 Add the modified standalone-openshift.xml to the container build. Via S2I build: Create a configuration directory in the top level of the pods git repository Place the modified standalone-openshift.xml in the configuration directory Rebuild the container and the modified XML will be copied into the container. Via Dockerfile build: Add an instruction in the Dockerfile to copy the modified standalone-openshift.xml file into the container COPY standalone-openshift.xml /opt/eap/standalone/configuration Rebuild the container and the modified XML will be copied into the container.
    • CLOUD Maintenance Sprint 16

    Description

      After scaling a pod down to 1, the logs are filled with the following error stack traces:

      ERROR [org.apache.activemq.artemis.core.client] (Thread-3 (ActiveMQxxxxxxxxxxxxxxxxx)) AMQ214016: Failed to create netty connection: java.net.NoRouteToHostException: No route to host: /IP:PORT
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
        at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:224)
        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:289)
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:528)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:38
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)2)
        at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
        at java.lang.Thread.run(Thread.java:748)

      Attachments

        Issue Links

          blocks

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-2282 Update the bind address fot http, https and AJP to accept any request

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          incorporates

          Task - Represents a small unit of work that is not end-user facing. CLOUD-2404 Adapt the messaging subsystem clustering config to current EAP best practice

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-2568 [EAP7.1] OpenShift image updates and fixes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. CLOUD-2404 Adapt the messaging subsystem clustering config to current EAP best practice

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              kwills@redhat.com Ken Wills
              rhn-support-trogers Travis Rogers (Inactive)
              Tomas Remes Tomas Remes
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: