Strategy « Transaction « JPA Q&A





1. how to assign different concurrency strategy to the same (persistence) entity?    stackoverflow.com

I'm using JPA and I am using second-level cache for all the reference entities. Everything's working well, I can get the entities from second-level cache is they were already been selected before. Now, ...

2. Transactional strategy for Hibernate L2 Cache    stackoverflow.com

If Hibernate L2 cache vendor supports "transactional" strategy, then does it mean that this cache guarantees the same level of isolation between transactions as specified in Hibernate config? For example, if cache ...

3. Commit Strategy    forum.hibernate.org

4. The chosen transaction strategy requires access to the JTA T    forum.hibernate.org

daoConfig.xml java:/comp/jdbc/Paymentsdb ${database.target} 3 jta com.atomikos.icatch.jta.hibernate3.AtomikosJTATransactionFactory com.atomikos.icatch.jta.hibernate3.TransactionManagerLookup on_close false

5. JTA - transaction strategy: SUPPORTS vs REQUIRED    forum.hibernate.org

Hi All - I'm using hibernate 2.1 and Spring M3, I think this question boils down to hibernate only: To use JTA transactions, I would like my hibernate session to participate when a transaction *already exists*, and otherwise, create a JDBC transaction. I don't see a way to do this, or that it is considered in the code - you can ...

6. Strategy for LOCK    forum.hibernate.org

In my project (an client server application, not a web app), different instances of the client, each having its own hibernate Session, may access the same object for update. The problem is that setting a lock on an object is Session-wide, it does not reach the DB level. hence two different sessions have two different lock level How do I set ...

7. transactional cache concurrency strategy problem    forum.hibernate.org

[hibernatedoclet] com.yahoo.gmmh.hibernate.Country [hibernatedoclet] ERROR [main] (XDocletMain.java:53) - Running XDoclet failed. [hibernatedoclet] ERROR [main] (XDocletMain.java:54) - <> [hibernatedoclet] D:\development\gmmh\yahoo\properties\wireless\gmmh\build.xml:310: XDoclet failed. [hibernatedoclet] at xdoclet.DocletTask.start(DocletTask.java:467)

8. Read committed not always maintained in read-write strategy    forum.hibernate.org

Hibernate version: 2.1.8 I think I've found some cases when read-write cache strategy doesn't maintain read comitted isolation level. First: Cached object is updated, then its lock is evicted from cache and session is flushed and cleared. Then updated object is loaded from database and put into the cache (still all in the same transaction). Other transactions can now see this ...

9. Commiting and rollback strategy failure    forum.hibernate.org

I am trying to insert rows into two different tables. Can any one please tell me why if an insertion into one table fails, the insertion into another table is not getting rollbacked in Hibernate. My sources are: Spring Bean Loader ...





10. Which transaction strategy should i use    forum.hibernate.org

Hi, I am having application with struts2 + mysql + hibernate simple DAO patter with Tomcat 5.x. i want to use hibernate transaction,can anybody suggest which one is the best suitable strategy for my application. My hibernate.cfg.xml(using c3p0 connection pooling/plain jdbc connection) Code: uname passwd ...

11. Optemistic Lock Strategy    forum.hibernate.org

Hibernate version: Hibernate 3 I have implemented optimistic lock (version) strategy an it works. But how can I resolve the collison after the Stale... Exception. I have some strategies. One is to ignore the exyecption an override the actual database record. But how can I do this ? First I have set the version attribute in the stale object to the ...

12. Change concurrency strategy of second-level cache on the fly    forum.hibernate.org

Hello, I use JPA and second-level cache in my project. They both worked fine so far. Now, I have two applications, 1.The read-only application just read data from database, it doesn't modify the database at all. Therefore, I choose the "READ_ONLY" concurrency strategy for the second-level cache, aiming at a better performance. 2.The read-write application read and write as well the ...