Yep - there's a bug. I've raised a JIRA [1] and fixed this on trunk. In reply to the second question re: "support to set certificates for TSL connection?". You can configure the client to use TLS, and if the server requires a client certificate, it believe it will check within the provided keystore for a certificate and provide if possible. There's no way of configuring the client to choose a specific certificate to send if there are multiple choices.
Hope this helps, Rob [1] https://issues.apache.org/jira/browse/QPID-4929 On 17 June 2013 12:30, Gordon Sim <[email protected]> wrote: > On 06/17/2013 02:19 AM, Brian wrote: > >> Hi, >> >> Can anyone help me? Thanks >> >> > Looks like your original message is awaiting moderator approval or > something(?): http://qpid.2158936.n2.nabble.**com/StackOverflowError-when- > **building-AMQP-message-**td7594137.html#none<http://qpid.2158936.n2.nabble.com/StackOverflowError-when-building-AMQP-message-td7594137.html#none> > > I'm not on the list of moderators, so can't change that myself but will > try and find someone who can. > > Regarding the problem, it sounds like some sort of infinite loop in > encoding. I don't know enough about the 1.0 java client to be able to tell > if that is a bug in the client library itself, or if something is not quite > as expected in your code (though it all looks fine, and certainly it > shouldn't have that outcome regardless). Rob, can you shed any light? > > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > >
