Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2128

We don't fire advisories unless we are started but we don't start till after consumers can connect

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • JBoss A-MQ 6.3.x
    • JBoss A-MQ 6.1, JBoss A-MQ 6.2.1, JBoss A-MQ 6.3
    • broker
    • None
    • +
    • Workaround Exists
    • Hide

      Shutdown the entire NoB and restart; other workarounds pending.

      Show
      Shutdown the entire NoB and restart; other workarounds pending.
    • Hide

      Setup 12 broker NoB;
      Consumer on broker A (prioritized between A and B)
      Producer on broker B (only)
      Failover consumer from A to B and it will connect back to A when A is available

      • If connection takes place before it can fire the advisory there is a problem
      Show
      Setup 12 broker NoB; Consumer on broker A (prioritized between A and B) Producer on broker B (only) Failover consumer from A to B and it will connect back to A when A is available If connection takes place before it can fire the advisory there is a problem

    Description

      2017-07-24 14:37:11,446 | DEBUG | 10.182.149:59734 | Connection:91 | port.logwriters.DefaultLogWriter 60 | 134 - org.apache.activemq.activemq-osgi - 5.9.0.redhat-611472 | RECEIVED: ConsumerInfo

      {commandId = 5, responseRequired = false, consumerId = BROKERB->BROKERA-37998-1500920814472-12:2:1:1, destination = ActiveMQ.Advisory.Consumer.>,ActiveMQ.Advisory.TempQueue,ActiveMQ.Advisory.TempTopic, prefetchSize = 1000, maximumPendingMessageLimit = 0, browser = false, dispatchAsync = true, selector = null, clientId = null, subscriptionName = null, noLocal = false, exclusive = false, retroactive = false, priority = 0, brokerPath = null, optimizedAcknowledge = false, noRangeAcks = false, additionalPredicate = null}

      forwarding bridge advisory consumer

      real consumer -
      2017-07-24 14:37:11,555 | DEBUG | .10.120.62:55256 | Connection:82 | port.logwriters.DefaultLogWriter 60 | 134 - org.apache.activemq.activemq-osgi - 5.9.0.redhat-611472 | RECEIVED: ConsumerInfo

      {commandId = 5, responseRequired = true, consumerId = ID:i7t450s-36975-1500921067184-1:1:1:1, destination = topic://TOITOPIC, prefetchSize = 32767, maximumPendingMessageLimit = 0, browser = false, dispatchAsync = true, selector = null, clientId = ID:i7t450s-36975-1500921067184-0:1, subscriptionName = null, noLocal = false, exclusive = false, retroactive = false, priority = 0, brokerPath = null, optimizedAcknowledge = false, noRangeAcks = false, additionalPredicate = null}

      should fire advisory...

      between:
      2017-07-24 14:37:11,555 | DEBUG | .10.120.62:55256 | Connection:82 | port.logwriters.DefaultLogWriter 60 | 134 - org.apache.activemq.activemq-osgi - 5.9.0.redhat-611472 | RECEIVED: ConsumerInfo

      {commandId = 5, responseRequired = true, consumerId = ID:i7t450s-36975-1500921067184-1:1:1:1, destination = topic://TOITOPIC, prefetchSize = 32767, maximumPendingMessageLimit = 0, browser = false, dispatchAsync = true, selector = null, clientId = ID:i7t450s-36975-1500921067184-0:1, subscriptionName = null, noLocal = false, exclusive = false, retroactive = false, priority = 0, brokerPath = null, optimizedAcknowledge = false, noRangeAcks = false, additionalPredicate = null}

      and a few lines down when it replies. We apparently don't fire advisories unless we are started but we don't start till after that consumer comes in...

      See the potential issue here

      Attachments

        Issue Links

          Activity

            People

              gtully@redhat.com Gary Tully
              rhn-support-rkieley Roderick Kieley
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: