Hibernate version:
3.2

Full stack trace of any exception that occurs:

org.hibernate.HibernateException: Unable to locate current JTA transaction
at org.hibernate.context.JTASessionContext.currentSession(JTASessionCont
ext.java:61)
at org.hibernate.impl.SessionFactoryImpl.getCurrentSession(SessionFactor
yImpl.java:542)
at org.jboss.hibernate.session.HibernateContext.getSession(HibernateCont
ext.java:94)

Name and version of the database you are using:
Oracle 9.2.0.6


Using EJB 3 Session Bean and with following attributes. I have set the Transcation Attribute Type to SUPPORTS for EJB.

========================================
@Stateless
@Remote(TestManager.class)
@TransactionAttribute(TransactionAttributeType.SUPPORTS)
@RolesAllowed("TestUser")
@SecurityDomain("TestSecurity")
@RemoteBinding(jndiBinding="TestManager")
public class TestSBean extends SessionBean implements TestManager
========================================


In one of the method implementation I am using

HibernateContext.getSession("java:/ZafeSessionFactory");

to get the Session and it throw above error.

org.hibernate.HibernateException: Unable to locate current JTA transaction


Here's the hibernate-service.xml

<server>
<mbean code="org.jboss.hibernate.jmx.Hibernate" name="jboss.har:service=ZafeHibernate">
<attribute name="DatasourceName">java:/ZafeDS</attribute>
<attribute name="Dialect">org.hibernate.dialect.Oracle9Dialect</attribute>
<attribute name="SessionFactoryName">java:/ZafeSessionFactory</attribute>
<attribute name="MaxFetchDepth">3</attribute>
<attribute name="ShowSqlEnabled">false</attribute>
<attribute name="Hbm2ddlAuto">update</attribute>
</mbean>
</server>

Any idea why?

According to the doc (http://www.hibernate.org/hib_docs/v3/re ... ansactions) you just have to do :

in a managed environment

You need a transaction to use Hibernate,
try Required instead of Supports

I have tried with "REQUIRES" and it works fine. I need to get it working with SUPPORTS.

Cheers,
Sanjay

You can't have no transaction and bind the current Session to the current (non-existing) transaction. Why do you want to use SUPPORTS? It's very rare that you can say "if a method on his bean is called, it's fine if a transaction context is present, but it doesn't matter if it's not there". Especially in a bean that does data access this makes not much sense.