qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Freeman <ke1g...@gmail.com>
Subject Re: Can we set a message "durable" via JMS?
Date Mon, 10 Feb 2014 22:07:01 GMT
Thanks much!

Bill


On Mon, Feb 10, 2014 at 5:00 PM, Robbie Gemmell <robbie.gemmell@gmail.com>wrote:

> In JMS the concept of message durability is handled via 'DeliveryMode',
> which can be either DeliveryMode.PERSISTENT or DeliveryMode.NON_PERSISTENT
> (essentially 'durable' and 'not durable'). This value defaults to
> PERSISTENT, and can be controlled by specifying it either on the producer
> itself, or in the send call when sending each message (but *can't* be
> controlled via the silly setDeliveryMode method on the Message instance,
> that is only for the JMS client itself to use and an application using this
> will have no effect on what a producer will do with a message when sending
> it).
>
> Robbie
>
> On 10 February 2014 21:37, Bill Freeman <ke1g.nh@gmail.com> wrote:
>
> > One part of our world uses JMS 1.1 to interact with C brokers (0.14, I
> > think).  We would like all messages sent this way to be durable.  I can
> do
> > this fine in the python API, but the JMS folks here tell me that JMS has
> no
> > support for such a thing.  They have tried specifying "Durable" and
> > "durable" header values, but these just become message properties (from
> the
> > Messaging API point of view), and the durrable message attribute remains
> > unset or false.
> >
> > Is there a way to mark the message durable using JMS?
> >
> > Failing that, can we configure the broker so that all messages arriving
> via
> > the JMS path are marked durable?
> >
> > Thanks, Bill
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message