Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-4287

Support GlobalSchedulerService to run in container manager transaction environment (e.g. ejb timer)

    XMLWordPrintable

Details

    Description

      Running inside CMT, GlobalJpaTimerJobInstance assumes transaction managment at command service level, disposing the runtime engine before transaction completion. Due to ContainerManagedTransactionManger the session is registered to be disposed after transaction ends. This raises an exception because the session was previously disposed.

      After discussion in user forums Maciej proposes a solution extending GlobalSchedulerService to decide if the transaction is managed by SchedulerService or not.

      Discussion here: GlobalTimerService and DisposableCommandService running in CMT

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users JBPM-4435 Timers fail when ContainerManagedTransactions are being used

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Feature Request - Feature requests from customers and/or users JBPM-3541 Container Managed Persistence

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Resolved

          Activity

            People

              swiderski.maciej Maciej Swiderski (Inactive)
              aartigao Alan Artigao (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: