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:
<camel:sslContextParameters id="sslContextParameters">
<camel:keyManagers keyPassword="{{key.password}}">
<camel:keyStore resource="{{keystore.location}}"
password="{{keystore.password}}" />
</camel:keyManagers>
</camel:sslContextParameters>
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 <camel:to/> 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.
