in reply to non-deterministic destructors?
It would be helpful if you'd list any warnings or error messages and the version number of the module. This will give others who'd like to look into the problem a place to start looking.
I just noticed the following in Camel 3 ed. It may or may not be helpful:
page 331:
Objects are always destroyed in a separate pass before ordinary references. This is to prevent DESTROY methods from using references that have themselves been destroyed.
conv
|
|---|