I'm debugging for days the behavior of NIO+SSL transport against the updateClusterClients, rebalanceClusterClients and updateClusterClientsOnRemove props.
I have a broker configured with two different transport conn: NIO and NIO+SSL, something like nio://0.0.0.0:61616 nio+ssl://0.0.0.0:61619 Client-side I specified a connection string that point to NIO+SSL connector. The point is that after a while the client switch from NIO+SSL to pure NIO. Is this the expected behavior for client? I would expect that a client does not change protocol. I'm using AMQ 5.9.0. -- View this message in context: http://activemq.2283324.n4.nabble.com/Updateclusterclients-attributes-specified-on-NIO-SSL-transports-tp4674570.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
