scottmf commented on PR #6085:
URL: 
https://github.com/apache/activemq-artemis/pull/6085#issuecomment-3564667884

   > I appreciate that the modifications to the reaper resolve the issue, but 
this is kind of like bailing water out of a boat with a hole in it. I would 
much rather just plug the hole. In other words, we need to determine where 
exactly these resources are leaking and fix _that_.
   > 
   > If you can work up a real reproducer (i.e. not something using mocks), 
even if it uses standalone brokers, I can take it from there.
   > 
   > It's worth noting that duplicate detection is on by default for 
cluster-connections and lots of folks are using a cluster. If this was simple 
to reproduce I imagine this problem would have been reported long ago so my 
guess is that there's something fairly unique about your use-case.
   
   Yes, understood.
   
   Over the past day i've been digging into this actually from another angle.  
I see that none of the addresses in those caches are auto-deleted as they 
should be and that is a bit baffling.  I am cleaning the BRIDGE caches, but 
these caches seem like they should also be cleaned up.
   
   While looking into this, i noticed we have a durable queue that is 
subscribed to the same address that all of these other queues are using - 
`publish/#`.  I think this could be the core of my problem and the timing makes 
sense as to why we never encountered this until about 6 months ago as this is 
just about the time it was added.  The queue is added from an external service 
so it wasn't clear until now.
   
   Could you comment on that?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to