I've been faced with exactly the same problem and found out the problem to be
a small inaccuracy in the bin/activemq script (version 5.10.0), when the
ACTIVEMQ_USER variable is set to a dedicated system user AND this system
user does have /bin/csh in /etc/passwd defined as default shell instead of
I have a multi-node (static) network of embedded Artemis JMS brokers.
I'm wondering if there is a way to register a JMS listener to a topic,
but somehow distinguish between messages sent via the local broker and
those that come from different nodes in the 'cluster'?
I'd like to make sure, tha
i'm sorry, i just need to start 2 times to turn on the activemq, it will make
db-1.log, but all message pending gone
thank you all :D
--
View this message in context:
http://activemq.2283324.n4.nabble.com/cannot-start-activemq-after-deleting-db-14-log-in-kahadb-tp4717097p4717201.html
Sent from
I see a couple of options off the top of my head:
1) Make sure "messages sent via the local broker" have a unique, consistent
property and simply create your topic subscription to select those messages.
2) Modify your cluster-connection configuration so that the topic in question
isn't clus
Can you please submit a bug report in JIRA for this?
On Sep 29, 2016 5:34 AM, "rkrell" wrote:
> I've been faced with exactly the same problem and found out the problem to
> be
> a small inaccuracy in the bin/activemq script (version 5.10.0), when the
> ACTIVEMQ_USER variable is set to a dedicate
