And the same applies to LevelDB within ActiveMQ 5.x; it's deprecated
because no one was willing to spend time fixing bugs and providing support
on the mailing list. If someone (or better, several people) were willing
to do that, it could be un-deprecated. But since the current reality is
that cur
Update: The message finally got consumed after about 2 days. Was this because
of some hanging client? How can I troubleshoot it?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Message-stuck-in-queue-tp4720713p4720721.html
Sent from the ActiveMQ - User mailing list archiv
ActiveMQ 5.13.4 with kahadb
There are some stuck messages left in one of my queues. The messages are
produced several days ago and it seems they will never be consumed. I can
see from the web console they are in the queue. Though new messages are
produced and consumed in the same queue without prob
There are currently no plans to revisit KahaDB replication that I know of.
But contributions are welcome so it's always possible someone could pick it
up. At this point the main focus has become Artemis since that already
supports replication.
On Wed, Dec 21, 2016 at 12:22 PM, mlange wrote:
> A
Another thing:
If you need a master/slave configuration... You may want to check out Apache
Artemis, which does "store replication"
--
View this message in context:
http://activemq.2283324.n4.nabble.com/LevelDB-vs-KahaDB-for-master-slave-Zookeeper-setup-tp4720633p4720699.html
Sent from the Act
(Replicated)LevelDB has some issues, and is indeed deprecated.
KahaDB does not officially have a replicating version. There has been some
work on it, which was abandoned in favor of ReplicatedLevelDB... If and when
this will be revived is unknown.
Then to the statement:
I need to implement a maste
