Not sure if this will turn out to be helpful or spam but I've previously encountered this error message and added the following to our kb:
This is related to an invalid SSL certificate and has been observed in a situation where the address used to contact the server did not match that of its certificate, eg: using "localhost" instead of "localhost.localdomain" or using a DNS alias which does not exist in the certificate. Depending on the client, the error may be accompanied by a message on the client such as "[Security] warning Connect failed: Failed: Unable to communicate securely with peer: requested domain name does not match the server's certificate. [-12276] " HTH! On 6 March 2015 at 16:08, Gordon Sim <[email protected]> wrote: > On 03/06/2015 04:02 PM, Gordon Sim wrote: > >> Doh, I was looking at the wrong code. Of course, its the NSPR based >> socket implementation, which has an alternative way of retrieving the >> error message. I'll raise a JIRA. >> > > Just fyi for anyone interested: https://issues.apache.org/ > jira/browse/QPID-6435 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- *Chris Richardson*, System Architect [email protected] *FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norwaywww.fourc.eu <http://www.fourc.eu/>* *Follow us on LinkedIn <http://bit.ly/fourcli>, Facebook <http://bit.ly/fourcfb>, Google+ <http://bit.ly/fourcgp> and Twitter <http://bit.ly/fourctw>!*
