On 4 June 2015 at 10:28, Robbie Gemmell <[email protected]> wrote: > On 4 June 2015 at 08:01, Erik Aschenbrenner <[email protected]> wrote: >> Ok thanks, >> >> I created my connection URI by using the new options now. >> >> First of all, I had to find out, that the URI option for the client ID has >> to be "jms.clientID" instead of "jms.clientId" which gives following >> exception: >> > > Nabble (or the mailing list itself) seems to have swallowed the > stacktrace, but I can guess what it said. As you note the > documentation is incorrect, I will update it. > > The reason for the disparity is that the options are applied using the > relevant setter method and JMS named it ClientID so the method is > named setClientID accordingly. While typing up the docs, the more > typical syntax must have slipped through the fingers on that > character. >
I have corrected this at the source for the next release, and updated the docs on the website for the current release. >> >> >> This should be corrected in the client configuration documentation. >> >> But now there is another problem. I'm using this connection URI: >> >> >> and I'm getting following exception when creation the connection: >> >> >> Creating the ssl connection with the old client API and the same connection >> settings works fine. >> >> Any ideas what is the problem here? Seems that there is some problem with >> the certificate: >> > > As both you and Rob have already noted, that was due to (and sounded > like, even without seeing the stacktrace) the newer client validating > you give a hostname that matched the certificate in use (I believe via > either the subject alt name entries, or the CN. It is using the Java > 7+ built-in HTTPS hostname verifier), which it was not. > >> >> Regards, >> Erik >> >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://qpid.2158936.n2.nabble.com/Changing-from-old-Qpid-JMS-client-to-Qpid-JMS-0-2-0-tp7625652p7625808.html >> Sent from the Apache Qpid users mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
