Hi ffrenchm,
I just tested this feature and it works as expected.
When I start my second listerner on the same destination (which is
declared exclusive) then I get the following exception.
org.apache.qpid.transport.SessionException: ch=0 id=0
ExecutionException(errorCode=RESOURCE_LOCKED, commandId=2,
classCode=8, commandCode=1, fieldIndex=0, description=resource-locked:
Cannot grant exclusive access to queue message_queue
(qpid/broker/SessionAdapter.cpp:384), errorInfo={})
When you run your test case, could you please have a look at the
broker logs and see if there is any error messages?
You should see something like this
2009-mar-25 11:33:50 error Execution exception: resource-locked:
Cannot grant exclusive access to queue message_queue
(qpid/broker/SessionAdapter.cpp:384)
Also if you are using M4, could you please try with trunk and see.
Regards,
Rajith
On Wed, Mar 25, 2009 at 5:17 AM, ffrenchm <[email protected]> wrote:
>
> on the trunk when I open my JMSListener with this JNDI configuration :
>
> java.naming.factory.initial =
> org.apache.qpid.jndi.PropertiesFileInitialContextFactory
> connectionfactory.local =
> amqp://guest:gu...@clientid/testpath?brokerlist='tcp://127.0.0.1:26969'
> destination.TEST =
> direct://amq.direct//TEST?routingkey='TEST'&exclusive='true'&durable='true'
>
> and I do a qpid-config -a localhost:26969 queues I've this result (my
> JMSListener is always running):
>
> Queue Name Attributes
> =============================================
> TEST --durable
> reply-dekatonshir.6565.1 auto-del excl
> topic-dekatonshir.6565.1 auto-del excl
>
> Then I start second JMSListener with the same JNDI configuration and I do not
> have any error. The TEST queue is clearly not exclusive in this case...
>
> ++
>
>
> ffrenchm wrote:
>> So what I understand is that exclusive queue can be durable ! What do you
>> think about?
>>
>> Thanks
>>
> That's fine. You can create an exclusive and durable queue. However
> once the session that created it closes, it will no longer be
> exclusive. So if the broker is restarted (thus closing all open
> sessions), the queue will still be there but it will not be exclusive.
>
> -Ted
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>
>
>
>
> --
> View this message in context:
> http://n2.nabble.com/tests-on-exclusive-queue-tp2498394p2531417.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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]
