JBoss AS 6 and JPA. Feature or bug ??

[markboletti]

Hi all,

I have a Java EE 6 application packed in a .war file which is running on JBoss AS 6.0.0. The application contains EJB 3.1 which are packed into the Web application. In particular I have a method which insert some inserts using the EntityManager Api:

@Stateless

public class SaveKpi {

    @PersistenceContext(unitName = "userLocalDatabase")

    private EntityManager em;

    public void insert() {

        try {

            MetricTemp temp = new MetricTemp();

            temp.setContentObjectSid("22345");

            temp.setObjectNm("test");

            em.persist(temp);

        } catch (Exception e) {

            // TODO Auto-generated catch block

            e.printStackTrace();

        }

    }

}

However this results in a

12:18:32,859 ERROR [STDERR] javax.persistence.TransactionRequiredException: EntityManager must be access within a transaction

12:18:32,859 ERROR [STDERR]     at org.jboss.jpa.deployment.ManagedEntityManagerFactory.verifyInTx(ManagedEntityManagerFactory.java:157)

12:18:32,859 ERROR [STDERR]     at org.jboss.jpa.deployment.PersistenceUnitDeployment.verifyInTx(PersistenceUnitDeployment.java:318)

12:18:32,859 ERROR [STDERR]     at org.jboss.jpa.impl.tx.TransactionScopedEntityManager.verifyInTx(TransactionScopedEntityManager.java:105)

12:18:32,859 ERROR [STDERR]     at org.jboss.jpa.impl.tx.TransactionScopedEntityManager.persist(TransactionScopedEntityManager.java:205)

12:18:32,859 ERROR [STDERR]     at kpi.action.SaveKpi.insert(SaveKpi.java:66)

When trying from within a Bean Managed Transaction, insert is performed successfully.

@TransactionManagement(TransactionManagementType.BEAN)

public class SaveKpi {

    @PersistenceContext(unitName = "userLocalDatabase")

    private EntityManager em;

    @Resource

    public UserTransaction utx;

    public void insert() {

        try {

            utx.begin();

            MetricTemp temp = new MetricTemp();

            temp.setContentObjectSid("22345");

            temp.setObjectNm("test");

            em.persist(temp);

            em.flush(); 

            utx.commit();

        } catch (Exception e) {

            // TODO Auto-generated catch block

            e.printStackTrace();

        }

    }

}

Is it a bug or simply I cannot initiate an EJB CMT transaction from within the Web context....maybe I should pack the EJB in a .jar file and assemble all the application in a .ear package ?

Thanks a lot in advance

Mark

[jaikiran]

How do you lookup and invoke on the bean? What does the client code look like?

[markboletti]

Hello, thanks for your reply.

Actually I have tried both with a direct JSF action

<h:commandButton action="#{saveKpi.insert}"  />

but also passing through an EJB facade

<h:commandButton action="#{facade.insert}"  />

@Stateless

public class Facade {

@Inject

SaveKpi ejb;

  public void insert() {

        try {

            MetricTemp temp = new MetricTemp();

            temp.setContentObjectSid("22345");

            temp.setObjectNm("test");

            em.persist(temp);

        } catch (Exception e) {

            // TODO Auto-generated catch block

            e.printStackTrace();

        }

    }

However both these approaches fail :-(

Mark

}

[wolfgangknauf]

Hi Mark,

could you take a look at this: http://stackoverflow.com/questions/1084627/entitymanager-throws-transactionrequiredexception-on-merge-in-jboss-jsf-bean

Hopefully it helps to add "em.joinTransaction()"; to your "insert" method before calling "persist".

Best regards

Wolfgang

[markboletti]

Hello Wolfgang,

I've just tried. Unfortunately it does not solve the issue.

regards

mark

[pgmjsd]

What is managing your transactions?  If these backing beans are EJBs then I think they need to be deployed in the EJB container to get the transaction management behavior.   I've always deployed EJBs inside an EJB-JAR, and then packaged that up with the WAR in an EAR.   Seam will also manage transactions and the EM if you don't like EJBs.