> 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.
This makes sense to me.
I think if you look at the updateClusterClients behaviour you will see that the
broker will announce other net
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.
> Still, I cannot understand why a client initially connected to a ssl
> connector should switch to tcp just because server connectors specified
> updateclusterclients prop. both for nio and nio+ssl.
> And I cannot understand what role the PublishedAddressPolicy could have in
> this process either.
tcp connections?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Updateclusterclients-attributes-specified-on-NIO-SSL-transports-tp4674570p4674581.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
tcp connections?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Updateclusterclients-attributes-specified-on-NIO-SSL-transports-tp4674570p4674580.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> 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.
Hi Matteo,
I spent a lot of time debugg
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.
