Ok than. So is this an expected behaviour or should I raise a JIRA.
Thanks, Tomas Gordon Sim <[email protected]> 26/08/2011 13:14 Please respond to [email protected] To [email protected] cc Subject Re: C++ and Python client diferences On 08/26/2011 11:24 AM, [email protected] wrote: > Hi Gordon, > > Thank you for your reply. > But there is still one thing I do not understand. > > I have set the log level to trace+ on my broker and here is what I got > from the log when I have used the same same addres for python as well as > for c++ client. > > Python: > > 2011-08-26 12:13:08 trace > [email protected]:0: recv cmd 0: > {ExchangeQueryBody: name=response; } > 2011-08-26 12:13:08 trace > [email protected]:0: recv cmd 1: > {QueueQueryBody: queue=response; } > 2011-08-26 12:13:08 trace > [email protected]:0: recv cmd 2: > {QueueDeclareBody: queue=response.QPID_CLIENT.response_queue_1; > exclusive=1; auto-delete=1; > arguments={qpid.max_count:F8:int64(1000),qpid.max_size:F8:int64(1000000),qpid.policy_type:V2:4:str16(ring)}; > } > 2011-08-26 12:13:08 trace > [email protected]:0: recv cmd 3: > {ExchangeBindBody: queue=response.QPID_CLIENT.response_queue_1; > exchange=response; binding-key=response.QPID_CLIENT.response_queue_1; } > 2011-08-26 12:13:08 trace > [email protected]:0: recv cmd 4: > {MessageSubscribeBody: queue=response.QPID_CLIENT.response_queue_1; > destination=0; accept-mode=0; acquire-mode=0; } > 2011-08-26 12:13:08 trace > [email protected]:0: recv cmd 5: > {MessageSetFlowModeBody: destination=0; flow-mode=0; } > 2011-08-26 12:13:08 trace > [email protected]:0: recv cmd 6: > {MessageCancelBody: destination=0; } > 2011-08-26 12:13:08 trace > [email protected]:0: recv cmd 7: > {QueueDeleteBody: queue=response.QPID_CLIENT.response_queue_1; } > > C++: > > 2011-08-26 12:15:48 trace > [email protected]: recv cmd 0: > {ExecutionSyncBody: } > 2011-08-26 12:15:48 trace > [email protected]: recv cmd 1: > {ExchangeQueryBody: name=response; } > 2011-08-26 12:15:48 trace > [email protected]: recv cmd 2: > {ExchangeDeclareBody: exchange=response; type=topic; alternate-exchange=; > arguments={}; } > > C++ client will get 'ACL denied exchange declare request from > QPID_CLIENT@QPID9999' from the broker. So to make the C++ client to be > able to pass through I had to adapt the ACL rules and change the adress as > stated in my previous email. Right, the c++ client will issue a declare for the exchange when creating a sender or receiver. If 'create' is not enabled the passive flag will be true. The python client doesn't issue this declare, hence the difference in ACL rules required at present. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected] ---------------------------------------------------------------------------- Deutsche Börse Services s.r.o. Managing Directors/Geschäftsführung: Michael Gassmann, Mats Andersson. Limited liability company with registered office at Sokolovská 662/136B, CZ-186 00 Prague 8 recorded in the Commercial Register IC: 275 77 015. Maintained by the city court in Prague, Sec. C, File No. 116874. ----------------------------------------- Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet. The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited. Legally required information for business correspondence/ Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz: http://deutsche-boerse.com/letterhead
