The unauthorized exception will destroy the session. You need to handle the exception and recreate a new session. This behaviour is the same for python, c++ (or for that matter any amqp client).
Rajith On Mon, Apr 19, 2010 at 5:28 AM, Joan Bellver Faus <[email protected]> wrote: > > Hello, I'm using the c++ broker and java client, for authentication using > the SASL mechanism EXTERNAL. > > My question is that when a user tries excute an action that is not allowed > in the file acl, the broker I disabled the whole session, not may take > further action on that session, since I returned the same exception. > > Is there any way to handle this exception, warning the user, and can > continue executing other actions permitted?. > > Regards. > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
