cshannon commented on issue #1747: URL: https://github.com/apache/activemq/issues/1747#issuecomment-4031245391
@mattrpav - It looks like you cut out stuff from the stack traces, do you have any custom plugins or code or anything else that might be causing this? The reason I am asking is because I took a look and the following appears to be going on. 1. Thread number 1 is adding a new message to the cache but detects that the cache needs to be disabled because of memory. It first has to wait for any outstanding pending messages by waiting on their future where it's stuck. It's waiting for the future for a message which is presumably being handled by thread 2. 2. Thread number 2 is trying to add the message but is stuck waiting to acquire the KahaDB index lock. What's interesting is the output shows that Thread number 1 holds the index lock which thread 2 needs (ie deadlock). However in the stack trace you posted, I don't see anywhere that thread 1 would actually acquire the index lock. Nothing in that trace would grab that lock, it's internal to KahaDB. So that's why I am wondering if you cut out something relevant here that would show where that lock was acquired. -- 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
