-
Notifications
You must be signed in to change notification settings - Fork 942
ARTEMIS-5773: augment cleanup of caches #6085
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
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. |
|
In any event, you've got a handful of CheckStyle issues: For what it's worth, you can run this check locally using |
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 - Could you comment on that? |
|
Just to be uber clear, these are a sample of the queues. The issue is that the temporary queues aren't being cleaned up, and neither are their bridge counterparts. Could it be that fundamentally I've just his an edge case where amq should not clean these up, or is this the bug? (or am i off-track?) (This is from jmx) Here is the durable queue ( |
|
I would suggest making this a draft and working through the issue some more until it can be determined how to best address the underlying problem. |
Sounds good. I am actively working on reproducing this in a simplified form factor. I will make this a DRAFT until I have something more concrete in place to show the issue. |
|
@jbertram I just pushed an additional update that changes SimpleAddressManager.addressWasUsed(). It fixes the second issue I referenced in the repro. The repro appears to be completely fixed when using this change. All unit tests pass in the build, but it can definitely use some scrutiny. In poking around the changes in this area, the issue that I'm seeing seems very similar to ARTEMIS-4162.. |
Added extra cleanup of PagingManagerImpl.stores and PostOfficeImpl.duplicateIDCache kicked off from PostOfficeImpl.reapAddresses()