[castor-user] Readonly-Transactions and locks

[Bogeblad Mattias]

Hi all,   A simple question. I have an app where everything is readonly operations against castor. I load and query everything in Database.READ_ONLY-mode. My question is – sometimes during extreme load I still get “…doesn't exist or no lock exceptions” on a lot of objects I have read. I have tried both with db.rollback() and db.commit before close but both seems to want to lock the objects for some reason.   Is it ok to skip both rollbacks and commits in such a situation and only do db.close on the db? Would that help me? Is there any other tips on the issue on read locks. This mostly happens when I do a cache-eviction and a read simultaneously (uuhh, is that spelling right). In there a way to stop cache eviction and read to occur concurrently?   Regards Mattias Bogeblad     Mattias Bogeblad [EMAIL PROTECTED] www.modul1.se Mobile +46 (0)702 80 05 05 Phone +46 (0)31 748 84 00, Fax +46 (0)31 748 84 01 Vallgatan 27, SE-411 16 Göteborg, Sweden