Actually I don't have to do any actual writing to the database, as it happens during the SQL construction. I will see if I can try that as well.

//Alain

On 04/03/2013 13:12, [email protected] wrote:
Hi All!

My gut feeling still tells me it is something related to 
concurrency/multithreading.
As it occurs rarely, Alain can't you just start several threads in your java 
app/test which calls your event insert method in a loop as if there is a real 
event to handle? Maybe we can force the error to appear more frequently (well, 
or your database explodes, but nevertheless something will happen)...

Jens


And I am really curious what the root cause might be


Von meinem iPad gesendet

Reply via email to