I do not think the # signs are supposed to be used in the ACL rules for queue names, exchange names or routing keys. I think you have to use *. Or am I wrong?
Apart from that I'm not sure what is the binding URL you are using actually supposed to do. Is there some reason why are you using the old binding URLs in the JMS API instead of the addresses? Regards Jakub On Wed, Aug 22, 2012 at 2:29 PM, holger <[email protected]> wrote: > One more thing: Now I setup the inverse, a test for topics "T.1.1" to "T.4.4" > where I try to figure out the minimum settings. To my amusement I now also > require the permission to create a queue. If I allow all queues, it works. > If I try to limit it to the actual queue, it doesn't. > I tried adding "name=T.#", "routingkey=T.#", "queuename=T.#". No results. > > Can you tell me, why this queue is needed and what its name actually is? > > I think it would be very useful for the users if the User Guide also > mentioned for which keyword (such as queue) you can use which attribute > (such as passive). Many users probably don't know whether they are > binding/creating/consuming a queue or an exchange.. > > Regards, > Holger > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Why-does-QPID-create-the-exchange-amq-direct-tp7581190p7581197.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
