Ashish, are you setting the clientID setting on your clients, as documented
at the bottom of
https://activemq.apache.org/how-do-durable-queues-and-topics-work.html? If
not, then on reconnection it may be that the new connection is getting a
different client ID, resulting in a different subscriber n
The documentation you shared did not solve my issue, however, I have resolved
this issue. Below is the resolution for me for the people who will be facing
this problem in the future.
We need to add some query string parameters in broker URL to enable TLS 1.2
and SHA cipher support for .Net Framewo
Hello,
I have a question about the effects of the the scheduled pool max size
in artemis (2.10.1).
I had a recurring issue with an embedded artemis instance which I had
significant trouble to track down.
The application stack uses a small number (3) of internal consumers do
process messages, conne
Hello all,
We run Artemis embedded on our Spring service and occasionally get this
issue where all our producer threads become blocked so no messages can be
produced to queue (happened 3 times in 2 weeks). We produce both regular
and large messages to the queue. All we get during this time from ar
Network pinger solves it. Thank you!
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hello Tim,
Please find below the config
Config with kahadb
http://www.springframework.org/schema/beans";
xmlns:amq="http://activemq.apache.org/schema/core";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://
If the problem is still occurring with regular KahaDB, then KahaDB probably
isn't the problem. Can you share your full broker configuration, rather
than just snippets?
Tim
On Wed, Nov 20, 2019, 8:16 AM Jean-Baptiste Onofré wrote:
> Basically the same as you:
>
> ind
Basically the same as you:
Let me try with AMQP client.
I just commented the Jira.
Regards
JB
On 20/11/2019 15:49, Ashish Vaishno wrote:
> Hello Tim,
>
> I have tried to change mkahadb to standard kahadb as well in my dev
> environment. I still face the same issue.
>
>
>
I also created a ticket https://issues.apache.org/jira/browse/AMQ-7350
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hello Tim,
I have tried to change mkahadb to standard kahadb as well in my dev
environment. I still face the same issue.
I will create a JIRA bug for the same.
@JB would it be possible to share your config?
Regards
Ashish
--
Sent from: http://activemq.2283324.n4.nabble.com
Ashish,
If you convert from mKahaDB to the standard KahaDB configuration (in a
dev/test environment), does the problem disappear?
If so, please write a bug in JIRA for the problem. (this mailing list
thread is not sufficient to get a fix implemented). If not, we'll have to
keep trying to isolate
11 matches
Mail list logo
