I can't reproduce the problem, but we have heard of other users having this problem. But because I can't reproduce it, we might just have to try a few things to see if we can track down the problem.
Could you check your transaction isolation setting for MySQL? Can you try to find your mysql.ini file (under Windows) or my.conf (on Unix/Linux/Mac).
The mysql.ini (Windows) is usually in either your MySQL Server directory (e.g. C:\Program Files\MySQL Server 5.0) or in your Windows directory (e.g. C:\Windows).
The my.cnf (*nix/Mac) is usually in \etc.
Find the entry "transaction-isolation". It should be set to READ-COMMITTED:
transaction-isolation=READ-COMMITTED
What is it set to?
We have the cache (which is what is throwing the exception) set to match READ-COMMITTED.
I'm also looking into whether we can use a newer version of the caching software, as that has some different options.
Fiona
Posted by Fiona Malikoff