Hi All, We are having deadlock error at prod system. We are using "qpid-jms-client-0.45.0" to connect Azure ServiceBus. At this moment, we have not found any root cause of this problem. As this is prod system, so we can't enable qpid trace level login.
Could you please take a look on this issue and suggest if this is caused by qpid client or something else? Error Details - First error "2020-04-06T10:47:20.17Z","Suspected deadlocked threads: QpidJMS Connection Executor: ID:9d006669-51f1-4fdb-9529-fe4c72e2481d:62 Id=1383 is in BLOCKED on lock=org.mule.servicebus.Connector@511db1d is owned by JmsSession [ID:951ecf9f-4991-4eq1-9c5e-85c001fwwe00:64:1] delivery dispatcher Id=1309 | JmsSession [ID:951ecf9f-4991-4eq1-9c5e-85c001fwwe00:64:1] delivery dispatcher Id=1309 is in WAITING on lock=java.util.concurrent.locks.ReentrantLock$NonfairSync@4d039032 is owned by JmsSession [ID:951ecf9f-4991-4eq1-9c5e-85c001fwwe00:64:3] delivery dispatcher Id=1311 | JmsSession [ID:951ecf9f-4991-4eq1-9c5e-85c001fwwe00:64:3] delivery dispatcher Id=1311 is in BLOCKED on lock=org.mule.servicebus.Connector@511db1d is owned by JmsSession [ID:951ecf9f-4991-4eq1- 9c5e-85c001fwwe00:64:1] delivery dispatcher Id=1309 | " Complete error - Please refer attached file. ServiceBus_DeadLock_Errors.zip <http://qpid.2158936.n2.nabble.com/file/t396358/ServiceBus_DeadLock_Errors.zip> 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]
