I'm referring to the limit attribute of the tempUsage element in
activemq.xml. A sample can be seen at
http://activemq.apache.org/xml-configuration.html. It's not well formatted
for easy reading, but it's correct XML.
Tim
On Fri, Oct 5, 2018, 7:40 AM Dan Abayev wrote:
> I do not know what the
I do not know what the property for it is, what do i set to zero. I checked
out documentation and couldnt find anything for temp store.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
If you set a limit of 0 for it with producer flow control enabled, no
messages will be written to it. I don't remember offhand whether it'll
still create the KahaDB files on disk in that case, but if that's something
you care about, it's a simple test for you to do.
Tim
On Wed, Oct 3, 2018, 8:48
Hello everyone,
We are using Artemis 2.6.3 and would like to know if there is anything like the
Failover Transport we could configure for our client sessions.
(http://activemq.apache.org/failover-transport-reference.html)
Client should always connect to primary. If not, use the secondary. If
Sorry to have joined late, but Miroslav and Justin have completely coverred
what I wanted to do: totally agree on everything +100
I would add one thing: take a look here https://softwaremill.com/mqperf/
Look on how Artemis is being used there: MAPPED journal (with datasync off,
now on 2.6.x), but
Hi Tim,
> First, spinning up a replacement host is not instantaneous, so there will
> be a period of at least a minute but possibly several where the messages on
> that broker and storage volume will simply be unavailable to consumers.
In case you decide to use HA with shared store then it will
