artnaseef commented on issue #1731: URL: https://github.com/apache/activemq/issues/1731#issuecomment-4006423896
@jeanouii thanks for looking into it. The deadlock report I provided is from a broker running in production. If you look at the `asn-debug-jdbc-slow-exception` branch on my fork of the project, you'll see I added code to make reproducing the problem easy. The underlying cause is an exception thrown by the persistence adapter, which is hard to reproduce. I agree that running the cleanup on a separate thread could be an easy fix. Another possibility is to decide which order of acquiring the 2 locks is correct and make sure the second lock always happens only after the first one has been acquired. I do wonder why the critical section is needed for the two lists - perhaps there's a simpler fix there? -- 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
