Uploaded image for project: 'AMQ Clients'
  1. AMQ Clients
  2. ENTMQCL-2063

Qpid JMS logs failed connections when there is no need to

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 2.6.0.GA
    • qpid-jms
    • None
    • Hide

      Use any Qpid JMS client (I can provide one if necessary) with a connection URI like this:

      failover:(amqp://bogus,amqp://working_broker)

      where "bogus" is a host/port combination that does not correspond to a running broker, and working_broker is a host/port combination of a working broker. The client will connect to the working broker but, before it does, it will output message about the failed prior connection attempt.

      Show
      Use any Qpid JMS client (I can provide one if necessary) with a connection URI like this: failover:(amqp://bogus,amqp://working_broker) where "bogus" is a host/port combination that does not correspond to a running broker, and working_broker is a host/port combination of a working broker. The client will connect to the working broker but, before it does, it will output message about the failed prior connection attempt.

      The Qpid JMS connection factory supports a "failover" connection URI that can list multiple brokers. If a connection factory is used to obtain successive connections then, by default, the multiple brokers are tried sequentially until one succeeds.

      In a master/slave broker set-up, it is perfectly normal that some of the brokers listed in a URI are unavailable some of the time. Although the connection factory does connect successfully to the next available broker, it will output a message for each broker it has to try before it succeeds. The OpenWire (ActiveMQ) client does not do this – an error message is produced if none of the brokers is available, otherwise there is no logging.

      The behaviour of Qpid JMS does not prevent normal broker operation – it just fills the log with scary and misleading warning messages.

            jross@redhat.com Justin Ross
            rhn-support-kboone Kevin Boone
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: