On 09/09/2011 01:11 PM, Alex Kulyavtsev wrote:
On Sep 9, 2011, at 11:27 AM, Fraser Adams wrote:
It seems a very reasonable requirement to be able to provision
administratively created queues/exchanges/bindings/links etc. via broker
startup config.
Yes, it is desirable feature, especially for
On Sep 9, 2011, at 11:27 AM, Fraser Adams wrote:
It seems a very reasonable requirement to be able to provision
administratively created queues/exchanges/bindings/links etc. via
broker startup config.
Yes, it is desirable feature, especially for non-durable queues. I
believe java broker
447733312563
richard.fal...@atos.net
-Original Message-
From: Carl Trieloff [mailto:cctriel...@redhat.com]
Sent: 08 September 2011 17:27
To: users@qpid.apache.org
Subject: Re: Durable Queue Behaviour
make the queue durable on create, but do not set the durable bit on
message publish. That
Carl Trieloff [mailto:cctriel...@redhat.com]
Sent: 08 September 2011 17:27
To: users@qpid.apache.org
Subject: Re: Durable Queue Behaviour
make the queue durable on create, but do not set the durable bit on
message publish. That should do it for you
Carl.
On 09/08/2011 11:47 AM, rfallon wrote:
Hi,
what scenario are you trying to solve?
You can definitely make a queue durable then specify that the message
isn't persistent. I'm pretty sure though (at least with Java anyway)
that the default is for messages to be specified persistent (see
javax.jms.Message javadoc):
||
|*DEFAULT_DEL
make the queue durable on create, but do not set the durable bit on
message publish. That should do it for you
Carl.
On 09/08/2011 11:47 AM, rfallon wrote:
> All,
>
> I want durable queues that DO NOT persist the messages, i.e. I want my
> configuration to survive a restart but (as a perform
