Re: ]: RE: : Re: WARNING log message to be removed

Francois, I have two apologize, I've misled you on two fronts. First, I had wrongly assumed that setting persistent=false on the broker resulted in setting persistent=false on the incoming messages, but based on the information in your logs I took a look into the code (specifically

Re: Re-ordering of messages - Artemis

I responded to your same post over on Stackoverflow [1]. In order to avoid confusion it might be best not to post the same question in multiple places. Justin [1] https://stackoverflow.com/questions/47333287/re-ordering-of-messages-artemis On Thu, Nov 16, 2017 at 6:34 AM, alisu

Re-ordering of messages - Artemis

In my use case, I have to run two instances of the same application that read messages from 'queue-1' and write them back to another queue 'queue-2'.  I need my messages inside the two queues to be ordered by specific property (sequence number) which is initially added to every message by

RE: ]: RE: : Re: WARNING log message to be removed

Hello Tim, Sorry to come back to you. I think I have understood the purpose of the 3 stores (persistent, memory and temp). But, I remind you that I used TomEE 7.0.4 plus flavor with ActiveMQ 5.14.5 with the following settings: - no activemq.xml file - BrokerXmlConfig =

Re: Messages stuck in broker

The inactivity monitor is supposed to keep the connection from timing out, but clearly that's not happening. You haven't done anything to intentionally disable its keepalive feature, have you? I don't see anything in your config files, but I want to make sure. Tim On Nov 13, 2017 3:54 AM,

Re: Messages stuck in broker

I believe that no messages are being passed because you haven't enabled any destinations to be sent across the network bridge. I see you're excluding some, but you're not including any so the exclusion has no effect. Tim On Nov 13, 2017 2:59 AM, "Shobhana" wrote: > Hi, >

Re: NPE when using a file based cursor with durable topic subscriptions

We need this one badly because it breaks all possibilities for message expiration on durable topics. I would provide a fix but I am lacking sufficient understanding of the code flow around cursors and the message store ;-) -- Sent from: