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

[GSS](7.4.z) AMQ172015: Can not connect to XARecoveryConfig

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.4.10.CR1, 7.4.10.GA
    • 7.4.8.GA
    • JMS
    • None

    Description

      In EAP 7.4 it is possible to define connections outside the default broker. When periodic recovery is trying to recovery such XA resource it seems to fail because the port it's trying to use does not exist.

      WARN  [org.apache.activemq.artemis.service.extensions.xa.recovery] (Periodic Recovery) AMQ172015: Can not connect to XARecoveryConfig [transportConfiguration=[TransportConfiguration(name=, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=amq-broker-cluster-local], discoveryConfiguration=null, username=quickuser, password=****] on auto-generated resource recovery: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.]

      In the above example the host is amq-broker-cluster-local but port is 443 since it's a SSL connection.

      I'm not sure why recovery process picks up port 61616 it is nowhere in my configuration.

      The configuration is setting up a JMS bridge between EAP and external AMQ 7.8.2 broker running in OCP.

       

      If the useTopology is set to false, reuse the initial connection connectors to connect to the broker for recovery

      Attachments

        Issue Links

          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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-24417 [GSS](7.4.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.
          • Verified

          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

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: