Hibernate version:2.1.7c

Mapping documents: Some classes setup with transactional cache

Code between sessionFactory.openSession() and session.close(): Managed by spring

Full stack trace of any exception that occurs: http://opensource.atlassian.com/project ... se/HB-1293

Name and version of the database you are using: Oracle 9i

The generated SQL (show_sql=true): Not relevant

Debug level Hibernate log excerpt: http://opensource.atlassian.com/project ... se/HB-1293



We see jbosscache 1.2 throwing the same exception when hibernate is configured using spring 1.1.3 via the usual spring idiom as explained in http://www.hibernate.org/110.html

Like this:

<bean id="myTransactionManager"
class="org.springframework.orm.hibernate.HibernateTransactionManager">
<property name="sessionFactory">
<ref bean="mySessionFactory"/>
</property>
</bean>

<bean id="myProductServiceTarget"
class="product.ProductServiceImpl">
<property name="productDao">
<ref bean="myProductDao"/>
</property>
</bean>

<bean id="myProductService"
class="org.springframework.transaction.interceptor.TransactionProxyFactoryBean">
<property name="transactionManager">
<ref bean="myTransactionManager"/>
</property>
<property name="target">
<ref bean="myProductServiceTarget"/>
</property>
<property name="transactionAttributes">
<props>
<prop
key="increasePrice*">PROPAGATION_REQUIRED</prop>
<prop
key="someOtherBusinessMethod">PROPAGATION_MANDATORY</prop>
</props>
</property>
</bean>

What I would like to learn is that in the reference doc of hibernate we have the following:

14.4.5. Strategy: transactional

The transactional cache strategy provides support for
fully transactional cache providers such as JBoss
TreeCache. Such a cache may only be used in a JTA
environment and you must specify
hibernate.transaction.manager_lookup_class.

But what I understand from posts in the fixed issue @ http://opensource.atlassian.com/project ... se/HB-1293

is that one should use HibernateTransactionManager instead of JTA
Is this contradicting with the reference doc?

In other words what I am asking is that how can we run spring/hibernate/jbosscache together?

Should one use JTA and configure jbosscache with a TxManager Lookup class or should it work fine simply by configuring the sessionfactory bean about the cacheprovider being jbosscache as in above?

No idea what HibernateTransactionManager is, so can't really answer your question. The explanation in the jira case seems pretty self-evident to me. There is a problem when both Hibernate and JBossCache are used in conjunction with JTA transactions; both try to register synchronizations with the ongoing transaction and it seems that the JBossCache synch is given precedence during afterCompletion callbacks which is the cause of the problem.

The solution is to simply use the Hibernate transaction API in your code as this alleviates the issue altogether. How does one acheive that with Spring? No idea; you'd probably have to ask the Spring guys. Typically you'd do something like:

Fixed by allowing non-transactional put()/get() in JBoss Cache 1.1.1.

Hi,

The HibernateTransactionManager of spring is of no significance here, when using it you end up with the same code as the one you mentioned being executed.

ie:

Session session = ...;
Transaction txn = session.beginTransaction(); // NOOP with ongoing JTA

// do my work

transaction.commit(); // Again, NOOP with ongoing JTA


The problem is that when we are not using JTA TxManager in a clustered environment, as told in the fix, we are still getting
net.sf.hibernate.cache.CacheException: org.jboss.cache.lock.TimeoutException:

I *seriously* doubt the spring classes are using the Hibernate Transaction API in the case of CMT. Please read entire responses, and not just the selective portion you wish to attune to.

We dont use spring over the top of CMT. We dont have any ejbs..

Please continue this discussion on the Spring forum then, it is clearly an obfuscated issue with Spring wrappers. If you'd like to continue in this thread, please only show Hibernate and or JBoss/JBossCache related code.

Ok thanks for the tip. If we talk about pure hibernate code. One should not use JTA and should not configure hibernate with a TxManager Lookup class. And one should use jobssCache v1.1.1 or above. Is that right?

http://www.hibernate.org/245.html

(Yes, this will somehow end up in the reference documentation.)