"[EMAIL PROTECTED]" wrote : Can you enable this in Hibernate to see if that solves the problem: | | hibernate.cache.use_minimal_puts | | Gavin and I have had a discussion on the potential problem. That, when using query cache, Hibernate will do a put on the JBossCache while retrieving from db. This can cause a long lock that resulting in TimeoutException. | | If this were the case, we will need to provide a way to get around this. | | -Ben
Ben, this solves the problem but of limied usage. use_minimal_puts works only for read-only entities, accounting this parameter applicable for the whole hibernate instance (not for particular entity) it is only useful when all your entities are read-only which is not true in most cases. I'd make emphasis, that problem is for any entity, not only declared read-only. I'm expecting, that unless I change and save entity or load it "for update", loading of entity is equivalent of simple sql select and will not cause any locking problem. For the moment, any read (hibernate's load()) can cause cache's put() (and therefore write lock) in case entity missed in cache. The problem appears not only as the result of using query cache (as described in your previous post), but with any of hibernate entity cached in TreeCache. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864340#3864340 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864340 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
