http://wiki.jboss.org/wikiJBossCacheHibernate JBoss Wiki: JBossCacheHibernate en http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=33&language=EN Line 15 was replaced by line 15
- * Use [the UserTransaction API|http://www.hibernate.org/42.html#A5] where possible. This will ensure Hibernate and JBossCache participate in transactions together, in the manner they've been designed to.
+ * Use [Hibernate's transaction API|http://www.hibernate.org/42.html#A5] where possible. This will ensure Hibernate and JBossCache participate in transactions together, in the manner they've been designed to.
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=32&language=EN Lines 25-27 were replaced by lines 25-26
- * If you are only using a query cache or collection cache, use REPL_ASYNC.
- * If you are only caching entities, use INVALIDATION_SYNC.
- * If you are using a combination of query caching and entity caching, use REPL_SYNC.
+ * If you are using a query cache or collection cache, use REPL_ASYNC.
+ * Otherwise, use INVALIDATION_SYNC.
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=31&language=EN Removed line 57
- * [JBossCacheHibernateTransactionsStandaloneExample]
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=30&language=EN Line 35 was replaced by line 35
- * If you are using __OPTIMISTIC__ locking, make sure you use the [OptimisticTreeCacheProvider|http://www.hibernate.org/hib_docs/v3/api/org/hibernate/cache/OptimisticTreeCacheProvider.html] that ships with Hibernate 3.2.x and higher.
+ * If you are using __OPTIMISTIC__ locking, make sure you use the [OptimisticTreeCacheProvider|http://www.hibernate.org/hib_docs/v3/api/org/hibernate/cache/OptimisticTreeCacheProvider.html]
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=29&language=EN Removed line 35
- * If you are using __OPTIMISTIC__ locking, make sure you use the [OptimisticTreeCacheProvider|http://www.hibernate.org/hib_docs/v3/api/org/hibernate/cache/OptimisticTreeCacheProvider.html]
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=28&language=EN Line 43 was replaced by line 43
- * Invalidation instead of replication. Allows for the cache to invalidate data on remote caches rather than broadcasting updated state. Improves efficiency and scalability, reduces network load, but make sure you use INVALIDATION_SYNC since INVALIDATION_ASYNC with Hibernate may introduce inconsistencies in edge cases (See [JBCACHE-806|http://jira.jboss.com/jira/browse/JBCACHE-806])
+ * Invalidation instead of replication. Allows for the cache to invalidate data on remote caches rather than broadcasting updated state. Improves efficiency and scalability, reduces network load. __Update__ Do not use INVALIDATION until [JBCACHE-806|http://jira.jboss.com/jira/browse/JBCACHE-806] is fixed! Until then please use REPL_ASYNC.
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=27&language=EN Removed line 28
- * Hibernate 3.2 has special support for JBossCache optimistic locking through org.hibernate.cache.OptimisticTreeCache
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=26&language=EN Removed line 10
- * Hibernate >= 3.2 is required if you plan to use Optimistic Locking.
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=25&language=EN Removed line 22
- ! Overall Recommendation:
Removed lines 24-26
- * If you are using a query cache or collection cache, use REPL_ASYNC.
- * Otherwise, use INVALIDATION_SYNC.
- * Always use Optimistic Locking as it improves concurrency.
At line 27 added 1 line.
+
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=24&language=EN Lines 18-19 were replaced by lines 18-19
- | REPL_ASYNC | Recommended for Query and Collection caches. Query cache requires REPL to work. | Does not provide as much concurrency as OPTIMISTIC
- | INVALIDATION_SYNC | Recommended for Entity Caches. Will not work correctly with Query cache. | Does not provide as much concurrency as OPTIMISTIC
+ | REPL_ASYNC | Recommended for Query and Collection caches | Does not provide as much concurrency as OPTIMISTIC
+ | INVALIDATION_SYNC | Recommended for Entity Caches | Does not provide as much concurrency as OPTIMISTIC
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=23&language=EN http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=22&language=EN Lines 17-20 were replaced by lines 17-20
- | REPL_SYNC | + data correctness for all caches. \\ - performance and scalability | Does not provide as much concurrency as OPTIMISTIC
- | REPL_ASYNC | Recommended for Query and Collection caches | Does not provide as much concurrency as OPTIMISTIC
- | INVALIDATION_SYNC | Recommended for Entity Caches | Does not provide as much concurrency as OPTIMISTIC
- | INVALIDATION_ASYNC | Better throughput and scalability than INVALIDATION_SYNC at the risk of data integrity when the network is stressed and in certain high-concurrency edge cases | Does not provide as much concurrency as OPTIMISTIC
+ | REPL_SYNC | + data correctness for all caches. \\ - performance | + data correctness for all caches. \\ - performance
+ | REPL_ASYNC | blah | blah
+ | INVALIDATION_SYNC | blah | blah
+ | INVALIDATION_ASYNC | blah | blah
Removed line 24
-
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=21&language=EN At line 11 added 1 line.
+ * Use asynchronous replication. Improves responsiveness of your application.
Line 17 was replaced by line 18
- | REPL_SYNC | + data correctness for all caches. \\ - performance | + data correctness for all caches. \\ - performance
+ | REPL_SYNC | blah | blah
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=20&language=EN Removed lines 17-24
- || ''CACHE MODE'' || OPTIMISTIC LOCKING || PESSIMISTIC LOCKING
- | REPL_SYNC | blah | blah
- | REPL_ASYNC | blah | blah
- | INVALIDATION_SYNC | blah | blah
- | INVALIDATION_ASYNC | blah | blah
-
-
-
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=19&language=EN Line 30 was replaced by line 30
- * Invalidation instead of replication. Allows for the cache to invalidate data on remote caches rather than broadcasting updated state. Improves efficiency and scalability, reduces network load. __Update__ Do not use INVALIDATION until [JBCACHE-806|http://jira.jboss.com/jira/browse/JBCACHE-806] is fixed! Until then please use REPL_ASYNC.
+ * Invalidation instead of replication. Allows for the cache to invalidate data on remote caches rather than broadcasting updated state. Improves efficiency and scalability, reduces network load.
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=18&language=EN Lines 27-28 were replaced by lines 27-28
- !! Newer versions of JBoss Cache
- With JBoss Cache 1.3.0 or newer, you have additional features that improve integration with Hibernate.
+ !! The future
+ With [JBossCache 1.3.0 "Wasabi"|http://jboss.org/jbossBlog/blog/manik/2005/11/10/JBossCache_1_3_Wasabi.txt] (due for release by the end of Feb 2006), integration with Hibernate will improve significantly, providing features such as:
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=17&language=EN Removed lines 35-40
- !! Troubleshooting
-
- * Pessimistic locking - [ TimeoutException errors reported indicating that write lock could not be acquired after 0ms | WriteLockTimeoutAfter0ms]
- * Optimistic locking - [ DataNode version mistmatch errors reported even in non-concurrent environments | DataNodeVersionMismatchAtRoot]
-
-
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=16&language=EN Line 25 was replaced by line 25
- * See [http://jira.jboss.com/jira/browse/JBAS-2868?page=all]
+ * See http://jira.jboss.com/jira/browse/JBAS-2868?page=all
At line 26 added 2 lines.
+
+
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=15&language=EN Lines 23-25 were replaced by lines 23-26
- !! Specify Level 2 Cache Provider or Disable It
- * Bug in JBoss AS 4.0.4RC1: if you don't specify level 2 cache provider, Hibernate looks for ehcache-1.1.jar, even though the documentation indicates use_second_level_cache defaults to false.
- * See http://jira.jboss.com/jira/browse/JBAS-2868?page=all
+ !! Use TreeCache as Hibernate Level 1 Cache Provider
+ *This seems to work in hibernate.cfg.xml to use TreeCache as the level 1 cache provider:
+ ** <property name="cache.provider_class">org.hibernate.cache.TreeCacheProvider</property>
+ ** <property name="cache.use_second_level_cache">false</property>
Removed line 28
-
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=14&language=EN Removed lines 23-28
- !! Use TreeCache as Hibernate Level 1 Cache Provider
- *This seems to work in hibernate.cfg.xml to use TreeCache as the level 1 cache provider:
- ** <property name="cache.provider_class">org.hibernate.cache.TreeCacheProvider</property>
- ** <property name="cache.use_second_level_cache">false</property>
-
-
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=13&language=EN http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=12&language=EN Line 29 was replaced by line 29
- * A new TreeCacheProvider for Hibernate that makes use of the new [Options API|JBossCacheOptionsAPI].
+ * A new TreeCacheProvider for Hibernate that makes use of the new [Options API|BossCacheOptionsAPI].
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=11&language=EN Removed line 29
- * A new TreeCacheProvider for Hibernate that makes use of the new [Options API|BossCacheOptionsAPI].
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=10&language=EN Line 24 was replaced by line 24
- With [JBossCache 1.3.0 "Wasabi"|http://jboss.org/jbossBlog/blog/manik/2005/11/10/JBossCache_1_3_Wasabi.txt] (due for release by the end of Feb 2006), integration with Hibernate will improve significantly, providing features such as:
+ With [JBossCache 1.3|http://jboss.org/jbossBlog/blog/manik/2005/11/10/JBossCache_1_3_Wasabi.txt] (due for release in March 2006), integration with Hibernate will improve significantly, providing features such as:
Line 27 was replaced by line 27
- * [Optimistic locking|OptimisticNodeLocking]. Allows for greater concurrency and hence scalability.
+ * Optimistic locking. Allows for greater concurrency and hence scalability.
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=9&language=EN Removed line 28
- * See [hibernate-recommended-config.xml|http://anoncvs.forge.jboss.com/viewrep/JBoss/JBossCache/etc/META-INF/hibernate-recommended-config.xml] in /etc/META-INF on JBossCache's CVS tree for a sample config.
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=8&language=EN Removed line 29
- !! Related
Removed lines 31-35
- * [JBossHibernate]
- * [JBossCache]
- * [JBossCache documentation|http://docs.jboss.com/jbcache/]
- * [Hibernate docs|http://www.hibernate.org/5.html]
-
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=7&language=EN Line 21 was replaced by lines 21-22
- ** [http://opensource2.atlassian.com/projects/hibernate/browse/HB-1396]
+ ** http://opensource2.atlassian.com/projects/hibernate/browse/HB-1396
+ \\
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=6&language=EN Removed line 22
- \\
At line 23 added 1 line.
+
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=5&language=EN Removed lines 17-23
- !! Looking up a TreeCache instance in Hibernate
- * TreeCacheProvider looks for a (hard coded) treecache.xml config file in it's classpath.
- ** Extend or rewrite TreeCacheProvider to take in the config file name as a param or env variable.
- * Use org.jboss.hibernate.cache.DeployedTreeCacheProvider to look up a TreeCache deployed as an MBean in JBossAS.
- ** http://opensource2.atlassian.com/projects/hibernate/browse/HB-1396
-
-
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=4&language=EN Lines 8-9 were replaced by lines 8-10
- * JBossCache versions prior to 1.2.2 are not recommended for use with Hibernate, due to deadlock issues that may arise.
- * Hibernate versions prior to 3.0.2 are not recommended for use with JBossCache, for the same deadlock issues mentioned above.
+ * JBossCache versions prior to 1.1.1 are not recommended for use with Hibernate, due to deadlock issues that may arise.
+ * Hibernate versions prior to 3.0 are not recommended for use with JBossCache, for the same deadlock issues mentioned above.
+ * Currently recommended versions are JBossCache 1.2.x with Hibernate 3.x.
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=3&language=EN Line 5 was replaced by line 5
- This page discusses general best-practices and tips when using JBossCache with Hibernate. This is a live document and will continue to be updated.
+ This page discusses general best-practices and tips when using JBossCache with Hibernate.
Removed line 7
- !! Versions
Line 10 was replaced by lines 9-16
- * Currently recommended versions are JBossCache 1.2.x with Hibernate 3.x.
+ * Recommended JBossCache configuration options include:
+ ** Use asynchronous replication. Improves responsiveness of your application.
+ ** Do not use a cache loader. Redundant, and an unnecessary overhead.
+ ** Use an eviction policy to prevent the cache getting too large.
+ ** Use [Hibernate's transaction API|http://www.hibernate.org/42.html#A5] where possible. This will ensure Hibernate and JBossCache participate in transactions together, in the manner they've been designed to.
+ * With JBossCache 1.3 (due for release in March 2006), integration with Hibernate will improve significantly, providing features such as:
+ ** Invalidation instead of replication. Allows for the cache to invalidate data on remote caches rather than broadcasting updated state. Improves efficiency and scalability, reduces network load.
+ ** Optimistic locking. Allows for greater concurrency and hence scalability.
Removed lines 12-16
- !! Recommended JBossCache configuration options
- * Use asynchronous replication. Improves responsiveness of your application.
- * Do not use a cache loader. Redundant, and an unnecessary overhead.
- * Use an eviction policy to prevent the cache getting too large.
- * Use [Hibernate's transaction API|http://www.hibernate.org/42.html#A5] where possible. This will ensure Hibernate and JBossCache participate in transactions together, in the manner they've been designed to.
Removed lines 18-24
- !! The future
- With [JBossCache 1.3|http://jboss.org/jbossBlog/blog/manik/2005/11/10/JBossCache_1_3_Wasabi.txt] (due for release in March 2006), integration with Hibernate will improve significantly, providing features such as:
-
- * Invalidation instead of replication. Allows for the cache to invalidate data on remote caches rather than broadcasting updated state. Improves efficiency and scalability, reduces network load.
- * Optimistic locking. Allows for greater concurrency and hence scalability.
-
-
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=2&language=EN Line 3 was replaced by line 3
- JBossCache can be used as a 2nd level cache provider for Hibernate, providing clustered, transactional caching.
+ JBossCache can be used as a cache provider for Hibernate, providing clustered, transactional caching.
Removed lines 9-13
- * Recommended JBossCache configuration options include:
- ** Use asynchronous replication. Improves responsiveness of your application.
- ** Do not use a cache loader. Redundant, and an unnecessary overhead.
- ** Use an eviction policy to prevent the cache getting too large.
- ** Use [Hibernate's transaction API|http://www.hibernate.org/42.html#A5] where possible. This will ensure Hibernate and JBossCache participate in transactions together, in the manner they've been designed to.
Removed lines 15-16
- ** Invalidation instead of replication. Allows for the cache to invalidate data on remote caches rather than broadcasting updated state. Improves efficiency and scalability, reduces network load.
- ** Optimistic locking. Allows for greater concurrency and hence scalability.
http://wiki.jboss.org/portal/default/wiki/WikiPortletWindow?action=1&org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fviews%2Fwiki_view.xhtml&page=JBossCacheHibernate&version=1&language=EN This is first version of the page so it doesn't have diff yet