-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
AMQ-8049: Failed to start Apache ActiveMQ (mKahaDB / JMX) #984
base: main
Are you sure you want to change the base?
Conversation
fb04e9f
to
b7dc544
Compare
cd3b1e3
to
ea8bc4b
Compare
When using filtered adapter for topics or queues with perDestination on catch all, after restart it is possible to have duplicated adapters when there are destinations in metadata and as a result start will fail. Perdestination should not start adapter for directory read from filesystem which is already defined in configured adapters.
Hey @jbonofre I need help and consultation :). I keep getting some random fails in tests (locally on my machine I had few successes but also fails. On your pipeline there were only fails). They do not seem to be connected to my change (and when I rerun them locally then they work), but still I am not fan of giving to code review commit with failed verification. Do you have some hints what should I do and how you guys proceed in such cases? |
Let me take a look on this one. For the tests, it's possible we still have some flaky tests, let me do a pass on these tests. |
How does the error occur when the adapters are added via directory listing? There should not be duplication. |
When you have configuration like:
On first start everything works fine, but after restart in
in mentioned 'doStart' then it will try to register and start same adapter second time and corrupt index. |
@jbonofre - Did you have time to take a look? |
@jbonofre - any news? :D |
I'm resuming my test/investigation on this one. |
When using filtered adapter for topics or queues with perDestination on catch all, after restart it is possible to have duplicated adapters when there are destinations in metadata and as a result start will fail. Perdestination should not start adapter for directory read from filesystem which is already defined in configured adapters.