Hi, You may consider to setup the SSLContextParameters directly on the camel-http4 component. I just checked the change log and found out CAMEL-6417[1] may related to the exception.
[1]https://issues.apache.org/jira/browse/CAMEL-6417 -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On June 23, 2014 at 4:15:54 PM, damien ([email protected]) wrote: > Hi Stephan, > > Thanks for the reply. But I don't quite understand. I've only one set of ssl > context parameters and it should be only one instance: > > > > > password="{{keystore.password}}" /> > > > > Why the error says: > > Previous instance hashcode: 0x6523ff4a, New instance hashcode: 0x0 > > 0x0 looks like null. > > I suspect that it has something to do with recipient list, because if I'm > using without the dynamic part, it just simply works. > > More Observation shows that when first time delivery of the message after > restart of the server, this bit is passed. The message failed to send is > only because the destination service is not available. But in the following > retries, the error just happens. Is it anything to do with catching? > > Camel 2.12 seems to be breaking a lot of my existing code that have been > working with 2.8, especially recipientList. > > Many thanks > Damien > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Only-same-instance-of-SSLContextParameters-is-supported-tp5752688p5752695.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
