Just to follow up...
I updated the upgrade instructions for 2.18.0 [1] to make this more clear.
Justin
[1]
https://activemq.apache.org/components/artemis/documentation/latest/versions.html#2180
On Sun, Aug 22, 2021 at 8:51 PM Justin Bertram wrote:
> The change in question is from
ARTEMIS-3421.
> >
> > e.
> >
> > -Oorspronkelijk bericht-
> > Van: Justin Bertram
> > Verzonden: maandag 23 augustus 2021 03:51
> > Aan: users@activemq.apache.org
> > Onderwerp: Re: SSL error as of artemis 2.18.0
> >
> >
> &
The first bit is slightly more nuanced meaning there is another
possibility (which is what actually occurred in ARTEMIS-3421), so I
would state it a little differently:
Change the hostname value that is being connected to in the broker
config, so it can match against the existing certificate
the documentation on 18-aug, but in
> ARTEMIS-3421.
>
> e.
>
> -Oorspronkelijk bericht-
> Van: Justin Bertram
> Verzonden: maandag 23 augustus 2021 03:51
> Aan: users@activemq.apache.org
> Onderwerp: Re: SSL error as of artemis 2.18.0
>
>
> EXTERNAL SE
Justin,
You just saved me a lot of time, thx!
FYI, I see that Robbie updated the documentation on 18-aug, but in ARTEMIS-3421.
e.
-Oorspronkelijk bericht-
Van: Justin Bertram
Verzonden: maandag 23 augustus 2021 03:51
Aan: users@activemq.apache.org
Onderwerp: Re: SSL error
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
