Thanks, Justin.
I'm not entirely convinced there is a real cause for concern here. If the
> broker itself is configured to allow non-SSL traffic when it shouldn't that
> seems like a broker configuration problem. The bottom line is that the
> broker must be configured appropriately. There's only s
Hello Community,
This is a follow up to https://issues.apache.org/jira/browse/ARTEMIS-1157
I set up a cluster of Artemis Brokers (2.6.0) with master/slave replication
configuration.
Each broker is configured with:
1. *Acceptor*:
*sslEnabled=true;needClientAuth=true,enabledProtocols=...;enabledCi
