6 Replies Latest reply on Jun 25, 2010 5:54 AM by YATIM Khalid

    Seam and Quartz could not discover transaction status error

    YATIM Khalid Newbie

      I have configured seam to use quartz(1.8) for scheduling task.
      All seam to be ok but i have this error in my log file
      ERROR org.jboss.seam.contexts.Contexts could not discover transaction status


      NB : This error occurs evrytime the scheduler try to do the work which is well done.


      Why i'm getting this? how can'i avoid it?
      Thanks!

        • 1. Re: Seam and Quartz could not discover transaction status error
          Nikolay Elenkov Master

          Show quartz configuration and full stack trace.

          • 2. Re: Seam and Quartz could not discover transaction status error
            YATIM Khalid Newbie

            Here is my quartz config (located in seam.quartz.properties
            -----------------------------------------------------------------------
            org.quartz.scheduler.instanceName  Sched1
            org.quartz.scheduler.instanceId  1
            org.quartz.scheduler.rmi.export  false
            org.quartz.scheduler.rmi.proxy  false


            org.quartz.threadPool.class  org.quartz.simpl.SimpleThreadPool
            org.quartz.threadPool.threadCount  5


            org.quartz.jobStore.class  org.quartz.simpl.RAMJobStore
            -----------------------------------------------------------------------



            This is the only line I can locate in my log file
            ERROR org.jboss.seam.contexts.Contexts could not discover transaction status

            • 3. Re: Seam and Quartz could not discover transaction status error
              Nikolay Elenkov Master

              'Full stack trace' means all the lines that follow, 'caused by', etc.


              Not sure what the changes in Quartz 1.8 are, try with the newest 1.6.x and 1.7.x.




              • 4. Re: Seam and Quartz could not discover transaction status error
                YATIM Khalid Newbie

                Ok! I'll try it.


                It's the unique line in log, there is no caused by

                • 6. Re: Seam and Quartz could not discover transaction status error
                  YATIM Khalid Newbie
                  My first problem went out but i have a new scritical one :

                  my scheduler works fine until this warninq appear the nothing is done (the same messages are produced)

                  ---------------------------------------------------------------------------------------------------

                  10:46:00,015 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for
                  TX 0:ffff0a641286:126a:4c24782a:665 in state  RUN
                  10:46:00,062 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.BasicAction_58] - Abort of action id 0:ffff0a641286:126a:4c2
                  4782a:665 invoked while multiple threads active within it.
                  10:46:00,109 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action 0:ff
                  ff0a641286:126a:4c24782a:665 aborting with 1 threads active!
                  10:46:00,562 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for
                  TX 0:ffff0a641286:126a:4c24782a:665 in state  CANCEL
                  10:46:01,109 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for
                  TX 0:ffff0a641286:126a:4c24782a:665 in state  CANCEL_INTERRUPTED
                  10:46:01,156 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.TransactionReaper_6] - TransactionReaper::check worker Threa
                  d[Thread-31,5,jboss] not responding to interrupt when cancelling TX 0:ffff0a6412
                  86:126a:4c24782a:665 -- worker marked as zombie and TX scheduled for mark-as-rol
                  lback
                  10:46:01,250 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.TransactionReaper_10] - TransactionReaper::check successfuly
                  marked TX 0:ffff0a641286:126a:4c24782a:665 as rollback only
                  10:47:00,015 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for
                  TX 0:ffff0a641286:126a:4c24782a:85d in state  RUN
                  10:47:00,062 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.BasicAction_58] - Abort of action id 0:ffff0a641286:126a:4c2
                  4782a:85d invoked while multiple threads active within it.
                  10:47:00,062 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action 0:ff
                  ff0a641286:126a:4c24782a:85d aborting with 1 threads active!
                  10:47:00,562 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for
                  TX 0:ffff0a641286:126a:4c24782a:85d in state  CANCEL
                  10:47:01,062 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for
                  TX 0:ffff0a641286:126a:4c24782a:85d in state  CANCEL_INTERRUPTED
                  10:47:01,062 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.TransactionReaper_6] - TransactionReaper::check worker Threa
                  d[Thread-32,5,jboss] not responding to interrupt when cancelling TX 0:ffff0a6412
                  86:126a:4c24782a:85d -- worker marked as zombie and TX scheduled for mark-as-rol
                  lback
                  10:47:01,062 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats
                  .arjuna.coordinator.TransactionReaper_10] - TransactionReaper::check successfuly
                  marked TX 0:ffff0a641286:126a:4c24782a:85d as rollback only
                  -----------------------------------------------------------------------------------------------

                  I guess i have problem width my config but i can't detect the problem.