On 22 March 2018 at 12:35, Bryan Dixon <[email protected]> wrote: > Rob, I wouldn't know if messages are being stored or not. I'm assuming > they > are not since a broker restart causes the messages to be 'lost' but that's > just my assumption. >
OK - great, just checking > > At the end of day Keith is correct - the behavior is what I was wanting - > the messages don't appear to be persistent (to me persistent means stored). > It was just very confusing that the web admin UI was displaying Persistent: > true for messages and the JMS JMSDeliveryMode header also reported the > message as Persistent yet I defined on the web admin UI Persist Messages?: > NEVER. That's why I was concerned there was an issue. > > I'm also coming at this from a JMS perspective and not an AMQP one so that > could be causing my confusion - terminology differences. > > I think this is really just a broker presentation issue rather than a JMS/AMQP thing. Both JMS and AMQP basically say that properties like persistence shouldn't be changed by the network. They are effectively statements of requirements made by the sender of the message "I want this message to be stored persistently". In the case of setting the queue to never persist a message we are basically saying that we are deliberately ignoring the sender's wishes. Note (for instance) if you set up a DLQ for a queue with persist NEVER, and that DLQ did not have the persistence override, then if the message moved to the DLQ then it would be persisted (because the DLQ would respect the wishes of the sender as expressed in the message header information). -- Rob Bryan > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users- > f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
