Hi Frizz,
I have absolutely the same symptoms described in
http://activemq.2283324.n4.nabble.com/Excessive-number-of-connections-by-failover-transport-td4735849.html
Also using randomize=false&priorityBackup=true. After some time of work, client
spams the server with connections and after short
My clients connect to AMQ with this connection string:
(tcp://amq1:61616,tcp://amq2:61616)?randomize=false&priorityBackup=true
It works - for some time. But sooner or later my AMQ server becomes
unresponsive because the host it runs on runs out of resources (threads).
The AMQ server basically kill
Dear ActiveMQ users,
inside the user guide I was reading that the journal should not be placed on
NFS because of performance issues and I'm currently trying to build an image
for OpenShift with persistent volumes (which typically use NFS).
Do you know any guides on how to use Artemis in OpenShift
I don't know Spring boot but I suspect that .war in Wildfly-11-0 is servlet
which is triggered periodically to consume messages. The problem might be that
this server app with consumer is invoked periodically, consumer starts to read
messages from queue and then closes. After closing consumer me
Thanks for all the answers. It sounds like I can't quite achieve what I
want out of the box. (Which is not a surprise)
I'll have a look at the internal code and see how hard it will be to build
something custom that is basically a combination of a small non-persistent
in-memory queue, and a larger
Thing I forgot to mention: Both apps are Spring boot apps, but server app is
deployed as a .war file in Wildfly-11-0 and local app is started using
Spring boot's "bootRun" task.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
