From: <glassfish_at_javadesktop.org>
Date: Tue, 07 Aug 2007 12:24:36 PDT

Although the 2nd level cache is not technically cluster aware, there are some things you can do to make your application more cluster-friendly.

Here's an article about using cacheing and locking properly in TopLink - which should translate fairly well to TopLink Essentials:

http://www.oracle.com/technology/tech/java/newsletter/articles/toplink/toplink_caching_locking.html

Here's some documentation related to configuring your cache in TopLink Essentials:

http://www.oracle.com/technology/products/ias/toplink/JPA/essentials/toplink-jpa-extensions.html#TopLinkCaching

The following table contains an entry that shows how to do pessimistic locking in TopLink Essentials using a query hint:

http://www.oracle.com/technology/products/ias/toplink/JPA/essentials/toplink-jpa-extensions.html#QueryHints

Using some of the configuration described above, in combination with some of the JPA API such as the refresh API, you should be able to build a fairly cluster-friendly application.
[Message sent by forum member 'tware' (tware)]

http://forums.java.net/jive/thread.jspa?messageID=229896