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

AMQ214016: Failed to create netty connection: java.net.UnknownHostException: eap-1-x7sph

XMLWordPrintable

      Customer impact: Application on OpenShift using messaging (EAP in client-server scenario) stops working when migrating from EAP7 to EAP8

      On OpenShift use EAP as messaging client connecting to EAP server with embedded broker. On EAP 8 this solution stops to work.

      ERROR [org.apache.activemq.artemis.core.client] (default task-1) AMQ214016: Failed to create netty connection: java.net.UnknownHostException: eap-1-x7sph

      Note same solution/test works with messaging server based on EAP7. Comparing EAP7 and EAP8 logs, in EAP8 log there is this suspisious entry

      WARN  [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool -- 78) AMQ122005: Invalid "host" value "0.0.0.0" detected for "http-connector" connector. Switching to "eap-1-g9jx7". If this new address is incorrect please manually configure the connector to use the proper one.

      Digging deeper comparing EAP7 and EAP8 configuration it seems this part of configuration is missing in EAP8

      <outbound-socket-binding name=\"http-messaging\">
    <remote-destination host=\"${jboss.messaging.host:localhost}\" port=\"${jboss.http.port:8080}\"/>
</outbound-socket-binding>

        1. jms-client-1-xqptz.log
          59 kB
        2. eap8_config.xml
          5 kB
        3. eap7_config.xml
          5 kB
        4. eap-1-57nrt.log
          30 kB

              jdenise@redhat.com Jean Francois Denise
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: