Well, I use an embedded broker and the config file is not in a standard
activemq xml format. Thus the config entries are slightly different from
standard activemq ones:
<cnf:networkConnectors>
<cnf:networkConnector
uri="multicast://239.252.0.10" networkTTL="5"
duplex="true"
suppressDuplicateQueueSubscriptions="true"
decreaseNetworkConsumerPriority="true"/>
</cnf:networkConnectors>
<cnf:transportConnectors>
<cnf:transportConnector name="openwire"
uri="nio://10.0.3.30:61616?transport.soTimeout=60000"
discoveryUri="multicast://239.252.0.10"
updateClusterClients="true"
auditNetworkProducers="true" />
<cnf:transportConnector
name="tls-connector"
uri="nio+ssl://10.0.3.30:51619?needClientAuth=true&transport.soTimeout=60000"
updateClusterClients="true" />
</cnf:transportConnectors>
where updateClusterClients means update on removal and balance clients as
well. Besides, we set the following
<conditionalNetworkBridgeFilterFactory replayWhenNoConsumers="true" />
Configuration of second broker is similar.
Clients connect to tls-connector connector on port 51619 and point to the
first broker.
After few seconds they switch misteriously to the nio connector.
I hope I have enough time this week to put into practice your suggestions
and keep on working on this.
Thank you very much, I really appreciate your help.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Updateclusterclients-attributes-specified-on-NIO-SSL-transports-tp4674570p4674644.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
