This seems likely to be similar to the situation we discussed in May [1]. You have the delivery thread from one session, which necessarily holds its own session delivery lock while dispatching, in a situation it is also holding application-level lock(s), while then trying to perform operations on another connection/session that requires holding its session delivery lock too, which that session is already necessarily holding by its own message delivery thread during delivery, which is in turn waiting on getting the same application lock(s) held by the other session thread earlier, and so your application has created a cross-session-inter-application block upon itself.
There was a nuance to the earlier thread, in that one of the threads involved was actually running the connection ExceptionListener at the time due to an issue attempting delivery of the messages (which you traced to happening with messages you did certain management operations on), and was still holding the session delivery lock while it was doing that. Though this wasn't a client bug, it was something we could improve without issue by unlocking the delivery lock before doing that, and we did this in the 0.52.0 release early in June. Perhaps you should try using one of the newer releases instead of the same older version as before. There will also be another client release soon (perhaps next week), 0.55.0, after the next proton-j release is available, which will contain a very nuanced buffer/string-decoding related fix to string that could perhaps even have also been in play in your original issue. [1] https://lists.apache.org/thread.html/r93536c9040b79931f1eee99ba4f721335f5d7b8991ac3dfc50bd7d55%40%3Cusers.qpid.apache.org%3E On Thu, 12 Nov 2020 at 17:14, akabhishek1 <[email protected]> wrote: > > Hi Team, > > We are getting "Suspected deadlocked threads" error in PROD environment. We > are trying to find out root cause of this issue. > > Could you please give us any clue regarding below error, so we can proceed > further. > > Logs - > Suspected deadlocked threads: JmsSession > [ID:de300758-71f8-4fff-9d51-0a3e6dc01b88:9:10] delivery dispatcher > Id=41620240 is in BLOCKED on lock=org.mule.servicebus.SbusConnector@58e4b68c > is owned by JmsSession [ID:de300758-71f8-4fff-9d51-0a3e6dc01b88:9:7] > delivery dispatcher Id=41620237 | JmsSession > [ID:de300758-71f8-4fff-9d51-0a3e6dc01b88:9:7] delivery dispatcher > Id=41620237 is in WAITING on > lock=java.util.concurrent.locks.ReentrantLock$NonfairSync@26cc0a98 is > owned by JmsSession [ID:de300758-71f8-4fff-9d51-0a3e6dc01b88:9:5] delivery > dispatcher Id=41620235 | JmsSession > [ID:de300758-71f8-4fff-9d51-0a3e6dc01b88:9:5] delivery dispatcher > Id=41620235 is in BLOCKED on lock=org.mule.servicebus.SbusConnector@58e4b68c > is owned by JmsSession [ID:de300758-71f8-4fff-9d51-0a3e6dc01b88:9:7] > delivery dispatcher Id=41620237 | > > > Regards, > Abhishek Kumar > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
