With Qpid JMS and master/slave broker topology -- many connections reported as failed even though the application is working

Solution Verified - Updated -

Issue

A Java application uses a failover: URI to denote a master-slave broker pair, with AMQP communication provided by the Qpid JMS client runtime. One of the brokers is normally able to accept client connections, while one is on standby and does not.

The application logs many 'failed connections' messages like this:

2020-04-22 10:24:59 INFO org.apache.qpid.jms.provider.failover.FailoverProviderConnection attempt:[2] to: foo:61616 failed

even though it appears to be working correctly.

Environment

  • Red Hat AMQ

    • 6.x
    • 7.x
  • Red Hat Qpid JMS client runtime for AMQP

    • 0.45.0.redhat-00002 and earlier

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In