We need to be very careful when making changes around locking, especially when introducing new locks. The code has several locks across multiple classes and it's not very obvious what the expected strategy is. Therefore it's quite easy to get into deadlock situations. It's no secret the code base is a bit of a mess, and it's all the more reason why we need to be careful :)
Regards, Rajith --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
