Can you try with HawtDB 1.3 which has just been released.
And what version of Camel are you using?
I upgraded HawtDB and continue to observe same exceptions. Is the
I will be out of town for a little while. Could you zip up a sample project which this issue and create a ticket at Apache JIRA.
And double check your logic in your custom AggregationStrategy implementation. Maybe your strip off properties on the Exchange or something.
Why are you using exchangeId as the correlation id?
Its unique and thus you wont be able to correlate.