Hi Tim!
Ok, so for a HA ActiveMQ master-slave is not required any network of
brokers, isn't it?
For the messages we are losing. We see that all messages are sent but when
failover happens consumer stops listening messages. Does It makes sense with
a wrong configuration?
Thanks for your answer!
Hi
We have Active MQ and Zookeeper ensemble on 3 nodes. We observed that
ActiveMQ goes down for some reason ,which didn't reflected in the log,since
log is in debug mode & at it automatically attempts to start itself after
some time but fails to do due to below error.Can any one suggest why its
You would use masterslave for connections to a master/slave cluster from
another broker. So if broker C was connecting to the master/slave pair A/B,
then C would use a masterslave networkConnector to A/B. But A and B would
have no networkConnector to each other, and no masterslave
You're mixing your paradigms.
The persistenceAdapter portion of your config is all you need for a
master/slave cluster, *as long as* your activemq.data variable resolves to
the same value in both processes. (Both processes run on the same machine,
right?) If so, the second broker started will
We have used Spring boot to develop sender and consumer apps.
*SENDER:*
To send messages we used and API REST that sends 5000 messages to a topic.
If some convertAndSend fails (ActiveMQ node 1 killed) we retry it until the
failover.
This is my sender class:
@RestController
public class
Replicated LevelDB is not supported, primarily because there weren't people
who knew the code who were willing to maintain the code (and provide
support on this mailing list), and it's been years since I've seen anyone
answer a meaningful question about replicated LevelDB here. Although it's
Actually, you should be able to set the alwaysSyncSend via the URI by
adding =true to the end of your producer's URI, so you
should be able to continue using JmsTemplate.
Tim
On Fri, Nov 30, 2018, 7:30 AM Tim Bain You're mixing your paradigms.
>
> The persistenceAdapter portion of your config
Those are the names of the threads within the broker JVM, so no, there is
not a way to get them into the client logs.
This feels like an XY problem (http://xyproblem.info), so what are you
actually trying to do? Maybe there's a different way to do it than the one
you've thought of.
Tim
On Thu,
This feels like a question for WebSphere support, rather than ActiveMQ.
Unless there's some aspect of the question that's specific to using
ActiveMQ in the context of WebSphere, that wouldn't apply if you were using
a different JMS product?
And to be clear, I'd happily answer your question if I
