1 Reply Latest reply on Dec 3, 2007 8:19 AM by Mani

    Quartz callback persist issue

    Mani Newbie

      Hi,
      I have moved my seam application to 2.0 and to Quartz from the EJB timer. After that I am seeing that new records are not getting persisted in database from inside the callback object. Update of records seems to be fine. I tried with some tables that do not have any relationships with other tables and it persists the object for those tables. However if I try that in table which has some relationship to another table, EntityHome persist of the parent table fails giving exception as below:

      2007-12-03 14:55:26,913 ERROR [DefaultQuartzScheduler_Worker-2] util.LoggerStream (LoggerStream.java:152) - javax.persistence.TransactionRequiredException: no transaction is in progress
      2007-12-03 14:55:26,913 DEBUG [http-192.168.1.6-8443-2] seam.Component (Component.java:1966) - instantiating Seam component: org.jboss.seam.core.events
      2007-12-03 14:55:26,914 ERROR [DefaultQuartzScheduler_Worker-2] util.LoggerStream (LoggerStream.java:152) - at org.hibernate.ejb.AbstractEntityManagerImpl.flush(AbstractEntityManagerImpl.java:293)
      2007-12-03 14:55:26,914 DEBUG [http-192.168.1.6-8443-2] seam.Component (Component.java:1387) - initializing new instance of: org.jboss.seam.core.events
      2007-12-03 14:55:26,914 ERROR [DefaultQuartzScheduler_Worker-2] util.LoggerStream (LoggerStream.java:152) - at org.jboss.seam.persistence.EntityManagerProxy.flush(EntityManagerProxy.java:90)
      2007-12-03 14:55:26,914 DEBUG [http-192.168.1.6-8443-2] seam.Component (Component.java:1404) - done initializing: org.jboss.seam.core.events
      2007-12-03 14:55:26,914 ERROR [DefaultQuartzScheduler_Worker-2] util.LoggerStream (LoggerStream.java:152) - at org.jboss.seam.framework.EntityHome.persist(EntityHome.java:51)
      


      Anybody faced this before?, any suggestions on how I can debug this further and fix?

      This used to work fine when using the EJB based timer. Unfortunately I can't go back to EJB timer since the call back is not all working with my application which was fine even with 2.0CR1 and hence wanted to move to quartz.

      -- Mani.