Hi,
I'm facing a problem in my system due to the option rebalanceClusterClients.
As I can see when this option is enabled every time a new connection is
created a signal is sent to every connected client in the network and
every failover connection is closed and re-opened.
In my system it happens that when a producer (using failover tranport)
is inside a transaction and a new client connects then some of the
messages are dropped by KahaDB as beeing ssen as duplicates
Again, the rebalanceClusterClients option is very aggressive and
generates a lot of network/broker overhead in my system, when I have
something like 100 cons JVM , which get disconnected and reconnected
every time a new producer (which is sporadically spawned) gets in.
Can I realize a setup like this ?
- failover transport producers insiede a transaction do not
accept/silently drop the command to rebalance the cluster and reconnect
- not every client get reconnected at every new client attaches to the
cluster
thanks in advance
ActiveMQ is great
Enrico Olivelli
