Do you have a way that I can reproduce what you're seeing? FWIW, the log message saying "Queue uiEventQueue-d336918f-fc37-44b9-9aeb-7e09fa90ad86 is delivering reference..." happens when the broker delivers a message from a queue to a consumer, not when a message is routed to a queue.
Justin On Tue, Nov 5, 2019 at 7:45 AM pholik1 <[email protected]> wrote: > Hello Justin, > thnaks for reply. > Unfortunately this is not the case I've checked few times. > > I've dumped artemis data journal and there was no bindings on this topic. > > There is shortened and commented log what happend(and/or is happening): > > 16:37:14,419 TRACE > [org.apache.activemq.artemis.core.server.impl.ServerSessionImpl] > > send(message=CoreMessage[messageID=*17179879120*,durable=true,userID=7a683996-fcbd-11e9-9dce-0a58c0a80837,priority=4, > timestamp=Fri Nov 01 16:37:14 CET 2019,expiration=0, durable=true, > address=*MESSAGE_REPORTER_TOPIC*,size=4037,...SHORTENED...@792769859, > direct=true) being called > 16:37:14,419 DEBUG > [org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl] *Couldn't > find any bindings for address=MESSAGE_REPORTER_TOPIC* on > > message=CoreMessage[messageID=*17179879120*,durable=true,userID=7a683996-fcbd-11e9-9dce-0a58c0a80837,priority=4, > timestamp=Fri Nov 01 16:37:14 CET 2019,expiration=0, durable=true, > address=MESSAGE_REPORTER_TOPIC,size=4037,...SHORTENED...@792769859 > > 16:37:14,419 DEBUG [org.apache.activemq.artemis.core.server.plugin.impl] > AMQ843010: beforeMessageRoute called with message: > > CoreMessage[messageID=*17179879120*,durable=true,userID=7a683996-fcbd-11e9-9dce-0a58c0a80837,priority=4, > timestamp=Fri Nov 01 16:37:14 CET 2019,expiration=0, durable=true, > address=MESSAGE_REPORTER_TOPIC,size=4037,...SHORTENED...@792769859, > context: > org.apache.activemq.artemis.core.server.impl.RoutingContextImpl@520310bf, > direct: true, rejectDuplicates: true > 16:37:14,419 TRACE > [org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl] Message > after > > routed=CoreMessage[messageID=*17179879120*,durable=true,userID=7a683996-fcbd-11e9-9dce-0a58c0a80837,priority=4, > timestamp=Fri Nov 01 16:37:14 CET 2019,expiration=0, durable=true, > address=MESSAGE_REPORTER_TOPIC,size=4037,...SHORTENED...@792769859 > > Message is appended to journal: > > 16:37:14,419 TRACE > [org.apache.activemq.artemis.core.journal.impl.JournalImpl] scheduling > appendAddRecord::id=17179879120, userRecordType=45, record = > > CoreMessage[messageID=*17179879120*,durable=true,userID=7a683996-fcbd-11e9-9dce-0a58c0a80837,priority=4, > timestamp=Fri Nov 01 16:37:14 CET 2019,expiration=0, durable=true, > address=MESSAGE_REPORTER_TOPIC,size=4037,...SHORTENED...@792769859 > 16:37:14,419 TRACE > [org.apache.activemq.artemis.core.journal.impl.JournalImpl] scheduling > appendUpdateRecord::id=*17179879120*, userRecordType=32 > 16:37:14,419 DEBUG [org.apache.activemq.artemis.core.server.plugin.impl] > AMQ843011: afterMessageRoute message: > > CoreMessage[messageID=*17179879120*,durable=true,userID=7a683996-fcbd-11e9-9dce-0a58c0a80837,priority=4, > timestamp=Fri Nov 01 16:37:14 CET 2019,expiration=0, durable=true, > address=MESSAGE_REPORTER_TOPIC,size=4037,...SHORTENED...@792769859, with > context: > org.apache.activemq.artemis.core.server.impl.RoutingContextImpl@520310bf, > direct: true, rejectDuplicates: true > 16:37:14,419 INFO [org.apache.activemq.artemis.core.server.plugin.impl] > AMQ841010: routed message with ID: *17179879120*, result: *OK* > > Skipped few log lines about confirmation of recieved message, > and now delivering message to wrong queue: > > 16:37:14,425 TRACE [org.apache.activemq.artemis.core.server.impl.QueueImpl] > Queue *uiEventQueue-d336918f-fc37-44b9-9aeb-7e09fa90ad86 is delivering > reference > > Reference[17179879120]*:RELIABLE:CoreMessage[messageID=17179879120,durable=true,userID=7a683996-fcbd-11e9-9dce-0a58c0a80837,priority=4, > timestamp=Fri Nov 01 16:37:14 CET 2019,expiration=0, durable=true, > address=MESSAGE_REPORTER_TOPIC,size=4037,...SHORTENED...@792769859 > > (Log is filtered for messageID=17179879120) > > It still seems to me as wrong behaviour. I am trying with debugger to > issolate issue, but it's quite complex. > Any suggestions how to solve this? > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
