Hi Justin,
Yes.I agree that if we have shared store, we don't need to replication. But
it would good option to have jdbc (shared store) for lock only to avid the
split-brain issue as configuring 3 pair is not suitable for small
environment and 3 pairs add lot of complexity.
Thanks for the detail
Thanks for the info about the new process for edits, and for making this
one.
Tim
On Mon, Oct 14, 2019, 5:02 AM Robbie Gemmell
wrote:
> Your wiki updates wont actually make it to the website, as the wiki
> isnt used for the site anymore.
>
> The website source and generated content are now main
Hi there,
I'm looking for a nudge in the right direction as to how to retrieve the
list of queues in ActiveMQ using C# NMS.
My use case it to get the list of queues and then operate on each of these
queues individually.
Thanks a bunch.
*---*
*Luc Hebert*
I think this idea has merit, especially considering it's something that the
5.x code-base supports. There are lots of bits of pluggable functionality
in Artemis (e.g. metrics [1], security settings [2], etc.). This could
follow the same pattern where the plugin could be defined in broker.xml
with a
> ...many people use the replication to avoid a spof with shared store and
also perf with NVMe...
Fair enough.
> I dont see why we would discourage anyone in implementing that.
For what it's worth, I didn't mean to discourage anybody from implementing
anything. I was mainly trying to answer his
I would like to persist my data in a mongodb cluster instead of using kahadb
or mysql.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Justin i disagree many people use the replication to avoid a spof with shared
store and also perf with NVMe , simply having a shared store just for the
filelock sounds entirely sensible to me. I dont see why we would discourage
anyone in implementing that.
Get Outlook for Android
On Mon, Oct