On 13 May 2011, at 08:53, P.Kremen wrote: > Dear Damian,
>> Does it happen after an extended period? Or can it happen almost immediately? > Unfortunately, it is even problematic for us to reproduce the error ... seems > like an issue that appears after a few days running the web app on the > server, so not very early at all. Aha! Sorry, I really should have checked what you meant by 'random' before. What's happening is that your mysql connection is being closed (after a timeout) and 'magically' reconnected. However -- as I alluded to before -- autoreconnect is problematic: it looks like the connection stays up, but this is illusory and you get nasty side effects like losing temporary tables. As you said, you really need to use the pool properly and free resources. In the meantime all I can suggest is a horrible hack: how about not reconnecting, then checking whether the connection is still alive in getOntModel? Damian
