Thanks for determining that port-forwarding directly to the pods doesn't
work either. Would you mind checking whether port-forwarding to a NodePort
service succeeds? I'm glad to hear that a NodePort service works as
expected when accessed directly, but my goal in asking you to test that
The change in question is from ARTEMIS-3367 [1]. Since the hostname defined
in the SSL cert on your broker can't be verified then you should either get
a new cert for your broker for which the hostname *can* be verified or set
verifyHost=false on the connector for the cluster-connection.
I'll
Hello!
Since Artemis 2.18.0, the broker-broker connections (for clustering) refuse to
connect due to "Caused by: java.security.cert.CertificateException: No name
matching [hostname] found". I did not try any client connections yet, so these
might just have the same problem.
My setup is the
Hi Ben,
we experienced a similar behaviour on widlfly + activeq-rar with your exact
use case while using XA for both database and broker connections.
>From our checks both XA connections seemed configured correctly, we
supposed the problem was caused by the commit on phase 2 of the "2PC
algorithm"
