Details
-
Bug
-
Resolution: Done
-
Major
-
JBoss A-MQ 6.1, JBoss A-MQ 6.2.1, JBoss A-MQ 6.3
-
None
-
+
-
Workaround Exists
-
-
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
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
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
- causes
-
AMQ-6778 Loading...