Re: Broker-J Queue Message persistent override

On 22 March 2018 at 16:57, Rob Godfrey wrote: > On 22 March 2018 at 12:35, Bryan Dixon 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

Re: Broker-J Queue Message persistent override

On 22 March 2018 at 12:35, Bryan Dixon 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

Re: Broker-J Queue Message persistent override

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. 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

Re: Broker-J Queue Message persistent override

Getting back to the original question - do we have any evidence that the messages are actually being stored persistently, or is it just that fact that the messages say "persistent=true" when viewed through the API? As per my earlier replies, I believe that if the message is sent only to queues

Re: Broker-J Queue Message persistent override

Hi Bryan You are modifying the correct attribute on the queue. At the API level it is called Queue#messageDurability. Within the Queue UI it is labelled "Persist Messages". There is no good reason for the inconsistency in terminology here. My apologies for any confusion. >From your

Re: Broker-J Queue Message persistent override

Alex your response about queue attribute 'messageDurability' isn't what I had set to NEVER - it was the Persist Messages? attribute that I set to NEVER. I want to make sure I'm on the same page as you guys and I'll provide some screen shots to show what I did and saw. Firstly, my original post

Re: Broker-J Queue Message persistent override

Looking at this further, it seems to me that the optimisation is already implemented... in the org.apache.qpid.server.txn.*Transaction classes, calls to _transaction.enqueue(queue, message) are always guarded by if(queue.getMessageDurability().persist(message.isPersistent())) ; thus the store()

Re: Broker-J Queue Message persistent override

Alex, we should probably see if we can optimise this... If a message is only sent to queues which are non-durable or override message durability to never, then we could avoid storing the message (or at least immediately delete it from the store, and not wait for confirmation the message is in the

Re: Broker-J Queue Message persistent override

Hi Brian, A queue attribute 'messageDurability' set to NEVER will stop queue message entries from storing in the message store. Thus, on broker restart the queue entries would be removed. However, queue 'messageDurability' does not affect storing of message content. If you send a persistent

Broker-J Queue Message persistent override

We are using Broker-J 7.0.2. For a couple of Queues I've set setting Persist Messages? to 'Never'. However when sending a message via a Qpid JMS 0.30.0 client the messages are being stored as Persistent. I've tried both methods MessageProducer.send(Message message) and