Figured it out.
So the connection has a root mutex that is held by it's child objects such
as sessions, producers and consumers. When a session closes in this our
case, it locks the root mutex and then notifies the connection that an
exception (i.e. unauthorized operation) has occurred. Following that, the
connection tries to carry out some tasks (see next para) and for that it
needs to lock the same mutex and hence the deadlock.
What the connection tries to do upon exception notification is to decide if
the error is a "hard error" which always returns true (ironically) and then
tries to close all sessions and eventually the connection. Now that is a
different bug as what we get is a session-level exception (i.e. a publisher
in a session is not authorized to do some operation) and it is wrong to
close all other sessions and subsequently the connection as a result of
that.
I am going to check on this on the dev list. Will keep this thread updated.
Danushka
On Wed, May 11, 2011 at 4:34 PM, Danushka Menikkumbura wrote:
> Qpid client hangs while trying to close JMS session when its operation
> (publish/subscribe) is unauthorised on server side. The issue is that it
> does not receive connection close commands (AMQP frames) in this case and
> hence goes into a wait state.
>
> It was found while fixing [1].
>
> I am looking into the issue and will keep updated.
>
> [1] - https://wso2.org/jira/browse/CARBON-8942
>
> Thanks,
> Danushka
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
