This tells you that the messages were discarded by ActiveMQ because they had expired. Are your producers setting a time to live when sending messages?
Tim On Fri, Sep 15, 2017 at 5:42 PM, mtod <[email protected]> wrote: > I'm running ActiveMQ 5.10.0 with an embedded camel route. It's been running > fine until we connected the master to an instance 5.14.5. > > 5.10.0 Network Connector: > > <networkConnectors> > <networkConnector name="connector019" > duplex="true" networkTTL="2" > userName="${activemq.username}" password="${activemq.password}" > uri="masterslave:(tcp://XXX01.corp.local:61616,tcp://XXX02. > corp.local:61616,tcp://XXX03.corp.local:61616)"> > <excludedDestinations> > <topic > physicalName="mirth.applogger"/> > <queue physicalName="esb.>"/> > </excludedDestinations> > <staticallyIncludedDestinations> > <topic physicalName=">" /> > <queue physicalName=">" /> > </staticallyIncludedDestinations> > </networkConnector> > </networkConnectors> > > > Now I have been experiencing a lot of messages going to the DLQ. > > I looked at the messages and they don't seem to have anything wrong with > them I did notice the following: > > dlqDeliveryFailureCause java.lang.Throwable: TopicSubDiscard. > ID:localhost->fmiuseastp01-63022-1486246061090-100948:1:1:2 > > I'm not sure what this is telling me. > > Thanks > > Mike > > > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
