Re: ActiveMQ failover transport considers http URIs that share the same hostname/IP & port as duplicates - the path is ignored

Hi Paul- During a failover, the ActiveMQ client library must recreate the connection, session, producer and/or consumer context. A random ‘ack’ coming back to a broker that did not dispatch the message would be ignored. Keep in mind that during any sort of failover or HA scenario with any type

Re: Copy of duplicate delivery message in DLQ

Hello Laetitia- The message in the log is from the ActiveMQConsumer suppressing a duplicate, not a duplicate-from-store scenario. ‘sendDuplicateFromStoreToDLQ’ would not apply to this situation. Thanks, Matt Pavlovich > On Mar 17, 2023, at 9:22 AM, Laetitia wrote: > > Hi, > > After having

Re: artemis operator: MQ222141: Node Manager can not open file /opt/activemq-artemis-broker/data/journal/server.lock

Thank you for your suggestion, Inside the broker container i saw /opt/activemq-artemis-broker/data so the journal folder was not created. My colleague suggested setting podSecurityContext: fsGroup: 0 and it seem to work, i suppose it is due to the volume security Regards Thai Le

RE: artemis operator: MQ222141: Node Manager can not open file /opt/activemq-artemis-broker/data/journal/server.lock

Thai Le, Likely one of the intermediate directories is missing, but many other reasons are possible. Has the broker instance already been created inside your image? The usual trick is to add a long pause after the broker startup command, so e.g. ".../bin/artemis run; sleep 3600" That gives you

RE: ExpiryQueue counts

Thanks! [rg] John Lilley Data Management Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761 | john.lil...@redpointglobal.com From: Dondorp, Erwin Sent: Monday,

RE: ExpiryQueue counts

John, I usually put the following properties in the address-settings for the ExpiryQueue (and DLQ): * min-expiry-delay = 15 minutes * max-expiry-delay = 15 minutes * expiry-delay = 15 minutes * expiry-address = empty (everything in the required xml format of course) This way,

Re: Please help finding lost packet

Hey John, So we had a problem recently that we debugged into and the concept of credits is related to flow control implemented by the broker.  We had a situation where under load and potentially due to something else going on our side where messages stopped being delivered all together. And

RE: Please help finding lost packet

Hi David, If by that you mean lines like: 2023-03-18T03:01:57.255 [HpaMetrics-Background] AbstractProducerCreditsImpl.checkCredits:182 [] DEBUG - not asking for -1 credits on activemq.management 2023-03-18T03:01:57.255 [HpaMetrics-Background]

ExpiryQueue counts

Hi, Under some circumstances we see ExpiryQueue count grow quite large, over 10k. I think we know why this happens, and it may be unavoidable. My question is, will this high count impact the broker? If so, what is the recommended solution? Can and should we just consume the ExpiryQueue?

artemis operator: MQ222141: Node Manager can not open file /opt/activemq-artemis-broker/data/journal/server.lock

Hello, I asked the question in artemis cloud github discussion but I got no reply so maybe I will get better luck here. I am trying to enable persistence for my broker, here is the deployment plan section: ``` deploymentPlan: size: {{ .Values.replicas }} image: placeholder

MQTT retained messages and a Clustered Broker

Hi, I have a clustered broker setup using loadbalance feature. I am having trouble getting MQTT retained messages feature to have the same last messages available on each of the brokers in my cluster. I need each client that connects to any of the brokers in the cluster to receive all the