On 01/04/16 07:51, Toralf Lund wrote:
On 31/03/16 16:35, Gordon Sim wrote:
On 31/03/16 15:31, Toralf Lund wrote:
The reason why I assumed an exclusive *superscription* was that the
I meant subscription, of course :-)
queue is still there after the application stops. Aren't exclusive
queues su
On 31/03/16 16:35, Gordon Sim wrote:
On 31/03/16 15:31, Toralf Lund wrote:
The reason why I assumed an exclusive *superscription* was that the
I meant subscription, of course :-)
queue is still there after the application stops. Aren't exclusive
queues supposed to go way automatically?
Only
On 31/03/16 15:31, Toralf Lund wrote:
The reason why I assumed an exclusive *superscription* was that the
queue is still there after the application stops. Aren't exclusive
queues supposed to go way automatically?
Only if they are also auto-delete queues.
-
On 31/03/16 15:05, Gordon Sim wrote:
On 31/03/16 13:27, Toralf Lund wrote:
Hi,
I just encountered an issue related to running one of my QPid
applications in parallel by 3rd party software that receives from the
same queue. I notice that when I start the latter, the queue attributes
as reported
On 31/03/16 13:27, Toralf Lund wrote:
Hi,
I just encountered an issue related to running one of my QPid
applications in parallel by 3rd party software that receives from the
same queue. I notice that when I start the latter, the queue attributes
as reported by qpid-config change from
--durable
Hi,
I just encountered an issue related to running one of my QPid
applications in parallel by 3rd party software that receives from the
same queue. I notice that when I start the latter, the queue attributes
as reported by qpid-config change from
--durable --replicate=all --lvq-key=qpid.subj
