4 Replies Latest reply on Dec 14, 2006 2:10 PM by Gavin King

    Entity Manager Woes

    Mark Jones Newbie

      Ok I have oficially downgraded myslef to n00b after a large amount of previous success with seam.

      Basically I am trying to use the entity manager from an external thread. I have the entity manager.

      EntityManager em = null;
       try {
       jndi = new InitialContext();
       //TODO get name from settings
       EntityManagerFactory emf = (EntityManagerFactory)
       em = emf.createEntityManager();
       NrgOrder nrgOrder = em.find(NrgOrder.class, 1);
       } catch (Exception e) {
       } finally {
       try {
       if(jndi!=null) jndi.close();
       } catch (NamingException e) {

      the myEntityManagerFactory is the same one as seam references (I think) as defined by the following...

       <persistence-unit name="nrg2">
       <!-- <property name="hibernate.hbm2ddl.auto" value="create"/> -->
       <property name="hibernate.cache.use_query_cache" value="true"/>
       <property name="hibernate.show_sql" value="true"/>
       <property name="jboss.entity.manager.factory.jndi.name" value="java:/myEntityManagerFactory"/>
       <property name="jboss.entity.manager.jndi.name" value="java:/entityManager"/>
      <?xml version="1.0" encoding="utf-8"?>
       <component name="org.jboss.seam.core.init">
       <property name="debug">true</property>
       <property name="myFacesLifecycleBug">true</property>
       <property name="jndiPattern">my/#{ejbName}/local</property>
       <component name="entityManager" class="org.jboss.seam.core.ManagedPersistenceContext">
       <property name="persistenceUnitJndiName">java:/myEntityManagerFactory</property>
       <component name="org.jboss.seam.core.manager">
       <property name="conversationTimeout">300000</property>
       <component class="org.jboss.seam.core.Ejb" installed="false"/>

      I am able to load using the above snippet but no updates are taking place.

      I am calling close() with no joy. I tried calling flush() but i get

      14:17:30,375 ERROR [STDERR] javax.persistence.TransactionRequiredException: no transaction is in progress
      14:17:30,375 ERROR [STDERR] at org.hibernate.ejb.AbstractEntityManagerImpl.flush(AbstractEntityManagerImpl.java:293)
      14:17:30,375 ERROR [STDERR] at halvor.schedulers.PendingOrderQuartzTarget.execute(PendingOrderQuartzTarget.java:95)
      14:17:30,375 ERROR [STDERR] at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
      14:17:30,375 ERROR [STDERR] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

      If i try and use transaction EntityTransaction et = em.getTransaction();
      et.begin(); I get...

      14:19:00,156 ERROR [STDERR] java.lang.IllegalStateException: JTA EntityManager cannot access a transactions
      14:19:00,156 ERROR [STDERR] at org.hibernate.ejb.AbstractEntityManagerImpl.getTransaction(AbstractEntityManagerImpl.java:316)
      14:19:00,156 ERROR [STDERR] at halvor.schedulers.PendingOrderQuartzTarget.execute(PendingOrderQuartzTarget.java:91)
      14:19:00,156 ERROR [STDERR] at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
      14:19:00,156 ERROR [STDERR] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

      I am clearly missing something obvious so can someone point it out to me plesae.

        • 1. Re: Entity Manager Woes
          Norman Richards Master

          What is an "external thread"? Another app on the same server? A thread that you start from outside Seam but from within your app?

          • 2. Re: Entity Manager Woes
            Mark Jones Newbie

            I am using Quartz to invoke methods but I will have to admit to the inner working being 'magic' to me.

            I have just gone back to square one and tried a completely different approach as, since I last looked, quartz has EJB3 initilisation support.

            Ok I will not get the bijection capabilities I assume but will get a working EntityManager hopefully.

            Is this a far better approach?

            • 3. Re: Entity Manager Woes
              Norman Richards Master

              Yeah - sorry. It's kind of obvious from the stack trace where you are calling from.

              You really should be doing JPA stuff from an environment that manages transaction support. I don't know much about quartz or its EJB3 support, so perhaps there is some way to appropriately configure it. If you really need to manage the transaction yourself you can look up the javax.transaction.TransactionManager under java:/TransactionManager and manage it yourself. But I'd recommend using services that manage the tx for you.

              • 4. Re: Entity Manager Woes
                Gavin King Master

                Yeah, you got a problem because the Quartz threadpool is probably not really "kosher" in the container environment (it should really be using JCA to take advantage of a container threadpool). So I'm not sure if you will even be able to look up UserTransaction from that thread.

                I can see a couple of approaches:

                (1) like Norman says, try managing transactions using the TransactionManager (ugly!)
                (2) try using a non-JTA EntityManager, and a resource-local transaction on the EM

                JPA doesn't let you flush outside of a transaction.

                Note that this is not a Seam question, and the guys in the EJB3 forum might have better answers for this one that we do here.