Re: [Artemis] Error message in log file for cluster on v1.3

I can check if by directly setting SSL example with static connectors. This error message is appearing only when cluster is setup with TLS. -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-Error-message-in-log-file-for-cluster-on-v1-3-tp4713397p4728619.html Sent

Re: Artemis - Wild card - messages received but not acknowledged

A reproducible test-case is always the best way to get help on issues like this. Artemis ships with lots of examples. It's typically fairly trivial to modify one of those examples to reproduce straight-forward use-cases. You can share the modified example via your GitHub repo. Could you work up

Artemis - Wild card - messages received but not acknowledged

I have a consumer running and listening to aes.q.#, Messages sent to aes.q.1 , aes.q.2 are consumed by consumer but not acknowledged. Message still remains in queue. But if i listen to those specific queues aes.q.1, then message is received and acknowledged. any one using wild card on the

Re: [Artemis] Error message in log file for cluster on v1.3

Is all that really necessary to reproduce the problem? Part of the exercise in reproducing the problem is simplifying the user-case and configuration down to only what is absolutely necessary to duplicate the issue. Justin On Mon, Jul 17, 2017 at 1:56 PM, abhijith

Re: [Artemis] Error message in log file for cluster on v1.3

Yep will do that. Will it be fine If I give a docker compose file based on https://github.com/vromero/activemq-artemis-docker? I need to bring up couple of nginx load balancers with ssl offloading as well. I will set it up with self signed certs -- View this message in context:

Re: [Artemis] Error message in log file for cluster on v1.3

Artemis ships with a statically configured HA example called "replicated-failback-static" that's working fine in the 2.1.0 release. Perhaps you could provide a reproducible test-case based on that example. Justin On Mon, Jul 17, 2017 at 11:31 AM, Justin Bertram wrote: >

Re: [Artemis] Error message in log file for cluster on v1.3

Do you have a reproducible test-case or anything more you could share with regards to configuration? Right now we just have some log messages and high level explanation of the configuration. That's not really enough to diagnose the problem. Justin On Mon, Jul 17, 2017 at 10:46 AM, abhijith

Re: [Artemis] Error message in log file for cluster on v1.3

Resurrecting this thread as we are still facing this issue in v2.1. Any suggestions on how to take it out? There is no issue is performance or message delivery except filling up of logs. Its very annoying and makes debugging almost impossible. -- View this message in context:

Re: Transport scheme NOT recognized: [mqtt+nio]

You have to add the fusesource MQTT client to your dependency manager, as it seem they forgot to include it in the activemq-all.jar file Example with maven pom.xml org.fusesource.mqtt-client mqtt-client 1.12 -- View this message in

Re: Active Durable Subscriber status automatically changing to offline Durable Subscriber [5.14.1 Most Stable Version]

Thank you so much for your response. Issue is resolved after removing that parameter. Thanks & Regards, Tejas Ramchandra Sawant Tata Consultancy Services Ltd. QBPL, Phase-2, Hinjewadi Pune, Maharashtra. cell : +91-8055946458 Mailto: tejas.sawa...@tcs.com Website:http://www.tcs.com

Re: How to SYNC messages in Cluster without using persistence on the message broker

This is ActiveMQ 5.x, not Artemis, right? What do you mean by "SYNC"? If you mean "replicate the message so a copy exists on all three brokers and can be consumed from any of them, and delete it from all three when it's consumed from one", ActiveMQ 5.x doesn't do that. Artemis, however, does

Re: Active Durable Subscriber status automatically changing to offline Durable Subscriber [5.14.1 Most Stable Version]

A maxInactivityDuration of 0 will disable inactivity detection, whose purpose is to detect both idle TCP connections and TCP connections that died ungracefully (e.g. due to network partitions), so I believe that your addition of that parameter caused this behavior. What was the reason you set it

How to SYNC messages in Cluster without using persistence on the message broker

Hi There, I'm wondering if there is any way to sync/replicate the message without persisting on the message broker. I have THREE node ODL cluster and ActiveMQ runs on all the nodes (without knowing each other). There are few topics created and message producer on one of the nodes and would like

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

This is what is updated in the JIRA (FYI) - this not going to be fixed, may be: the priority support is not a good candidate for runtime modification because not only do the in-memory messages need to retained in priority memory, the store needs to retrieve and store messages in priority order.

client abort and can't connect server immediately

Hi, I am new to activemq artemis, I am using mqtt protocol. I use eclipse paho java client library to connect server. I find that when my program connect to server than then kill the program, (my program has no chance to call disconnect) then the client can't connect to server again, the client

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

Thanks Tim. Created https://issues.apache.org/jira/browse/AMQ-6772 -- View this message in context: http://activemq.2283324.n4.nabble.com/Active-MQ-runtimeConfigurationPlugin-Set-Message-Priority-Not-working-tp4728264p4728584.html Sent from the ActiveMQ - User mailing list archive at