*Background*
a. A work queue of messages.
b. There are multiple readers of the work queue.
c. At anyone time, there are transactional sessions reading messages from
the queue,
d. or messages that have been delivered to a client, but the message is
being processed and has not been acknowledged.
No network of brokers.
The JMSXGroupID is being used to block concurrent execution of the task.
Concurrent execution would cause one process to basically trash what the
other one is doing as well as present many opportunities for failure.
Your idea about a camel route/server to route the message
Try the following:
* Check the IP addresses each machine resolves for the other
* Check each machine for an internal firewall
* Use a packet sniffer on each machine and/or a third machine on the network
* Try to connect between the machine on another port
* Traceroute may tell you if the machines
Are the JMSXGroups required because messages need to be processed in order?
If not, remove the JMSXGroups and let messages distribute across the
consumers.
If ordering is an issue, then it may be necessary to look outside of
ActiveMQ to fully solve the problem. For example, it would be
straight-
Hi,
I've been trying to use ActiveMQ multicast transport for a couple of days,
without success, so I'm posting here in hope someone already achieved this.
What I'm trying to achieve:
I'm using topics, in a context where there are a lot of publishers and a
lot of subscribers, with messages
