<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Jboss Cache on The Dangling Pointer</title><link>https://aaron.blog/tags/jboss-cache/</link><description>Recent content in Jboss Cache on The Dangling Pointer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 14 Apr 2010 00:19:40 +0000</lastBuildDate><atom:link href="https://aaron.blog/tags/jboss-cache/index.xml" rel="self" type="application/rss+xml"/><item><title>Spring 3.0 + Hibernate 3.3.2 + JBoss Cache 2 + JTA = Fail</title><link>https://aaron.blog/spring-3-0-hibernate-3-3-2-jboss-cache-2-jta-fail/</link><pubDate>Wed, 14 Apr 2010 00:19:40 +0000</pubDate><guid>https://aaron.blog/spring-3-0-hibernate-3-3-2-jboss-cache-2-jta-fail/</guid><description>&lt;p&gt;I've spent the past two days trying to get a distributed secondary Hibernate cache working with a Spring 3 application.  The application is web-based running on JBoss 5.1 so I figured the best approach would be to use JBoss Cache, since it's automatically configured and available in JNDI when you use the "all" configuration.&lt;/p&gt;&lt;p&gt;Hibernate 3.3.2 is configured inside of Spring using the Annotation-based session factory bean.  Because I'm using JTA to manage transactions and Hibernate's current session, I need to make sure that the secondary cache, whatever I choose, is aware of the transaction manager.  I originally had EHCache 2.0.1 hooked into Hibernate via Hibernate configuration parameters passed into Spring's bean.  I was not setting the cache factory parameter on this bean.  Everything works fine in this configuration and it recognizes the JTA transactions.&lt;/p&gt;</description></item></channel></rss>