Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-24417

[GSS](7.4.z) JBoss throws UnknownHostExceptions and XARecovery fails when Connected to an AMQ Cluster in OpenShift

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Hide

      Configure JBoss messaging-activemq as a resource adapter targeting the load-balanced, node-port or headless routes for an AMQ cluster hosted in OpenShift:

              <subsystem xmlns="urn:jboss:domain:messaging-activemq:13.0">
            <remote-connector name="netty-remote-throughput-node1" socket-binding="messaging-remote-throughput-node1">
                <param name="ssl-enabled" value="true"/>
            </remote-connector>
            <remote-connector name="netty-remote-throughput-node2" socket-binding="messaging-remote-throughput-node2">
                <param name="ssl-enabled" value="true"/>
            </remote-connector>
            <pooled-connection-factory name="activemq-ra-remote" entries="java:/RemoteJmsXA java:jboss/RemoteJmsXA java:/jms/DefaultJMSConnectionFactory" connectors="netty-remote-throughput-node1 netty-remote-throughput-node2" ha="false" reconnect-attempts="0" use-topology-for-load-balancing="false" transaction="xa" user="admin" password="admin" >
                <inbound-config use-jndi="false" rebalance-connections="false" setup-attempts="-1" setup-interval="5000"/>
            </pooled-connection-factory>
            <external-jms-queue name="INBOUND_QUEUE" entries="java:/jms/queue/INBOUND_QUEUE"/>
            <external-jms-queue name="OUTBOUND_QUEUE" entries="java:/jms/queue/OUTBOUND_QUEUE"/>
        </subsystem>

      Deploy an AMQ broker cluster on openshift and expose its endpoint(s) to external clients.

      Alternative: You can simulate the same failures by configuring the AMQ cluster outside openshift, but in a multihomed environment, using one interface for clustering (node1.internal.test.redhat.com) using plain communication, and another interface for client communication using ssl (sample configs attached). Configure /etc/hosts so that the internal interface is mapped on the broker hosts, but not on the host where JBoss is deployed.

      Start JBoss EAP and wait some time. You will see UnknownHostExceptions and XARecovery failures as the resource adapter attempts to contact the "internal" broker endpoints.

      Show
      Configure JBoss messaging-activemq as a resource adapter targeting the load-balanced, node-port or headless routes for an AMQ cluster hosted in OpenShift: <subsystem xmlns="urn:jboss:domain:messaging-activemq:13.0"> <remote-connector name="netty-remote-throughput-node1" socket-binding="messaging-remote-throughput-node1"> <param name="ssl-enabled" value="true"/> </remote-connector> <remote-connector name="netty-remote-throughput-node2" socket-binding="messaging-remote-throughput-node2"> <param name="ssl-enabled" value="true"/> </remote-connector> <pooled-connection-factory name="activemq-ra-remote" entries="java:/RemoteJmsXA java:jboss/RemoteJmsXA java:/jms/DefaultJMSConnectionFactory" connectors="netty-remote-throughput-node1 netty-remote-throughput-node2" ha="false" reconnect-attempts="0" use-topology-for-load-balancing="false" transaction="xa" user="admin" password="admin" > <inbound-config use-jndi="false" rebalance-connections="false" setup-attempts="-1" setup-interval="5000"/> </pooled-connection-factory> <external-jms-queue name="INBOUND_QUEUE" entries="java:/jms/queue/INBOUND_QUEUE"/> <external-jms-queue name="OUTBOUND_QUEUE" entries="java:/jms/queue/OUTBOUND_QUEUE"/> </subsystem> Deploy an AMQ broker cluster on openshift and expose its endpoint(s) to external clients. Alternative: You can simulate the same failures by configuring the AMQ cluster outside openshift, but in a multihomed environment, using one interface for clustering (node1.internal.test.redhat.com) using plain communication, and another interface for client communication using ssl (sample configs attached). Configure /etc/hosts so that the internal interface is mapped on the broker hosts, but not on the host where JBoss is deployed. Start JBoss EAP and wait some time. You will see UnknownHostExceptions and XARecovery failures as the resource adapter attempts to contact the "internal" broker endpoints.

    Description

      When the JBoss EAP is running outside OpenShift with its messaging-activemq subsystem iconfigured as a resource adapter connecting to an AMQ cluster within OpenShift, we see UnknownHostExceptions and XARecovery failures due to topology updates, even if useTopologyForLoadBalancing is set to false and even if ha is also set false.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-25239 [GSS](8.0.z) JBoss throws UnknownHostExceptions and XARecovery fails when Connected to an AMQ Cluster in OpenShift

          • 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.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-18756 WildFly throws UnknownHostExceptions and XARecovery fails when Connected to an AMQ Cluster in OpenShift

          • 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.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-24383 [GSS](7.4.z) Upgrade artemis-wildfly-integration from 1.0.4 to 1.0.7

          • 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 related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-24522 [GSS](7.4.z) AMQ172015: Can not connect to XARecoveryConfig

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7541 JBoss throws UnknownHostExceptions and XARecovery fails when Connected to an AMQ Cluster in OpenShift

          • 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.
          • Release Pending

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-25600 [GSS](7.4.z) WFLY-18212 - If the messaging HA cluster is not full started then the transaction recovery will be misconfigured

          • 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

              istudens@redhat.com Ivo Studensky
              rhn-support-dhawkins Duane Hawkins
              Votes:
              1 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: