Uploaded image for project: 'JBRULES'
  1. JBRULES
  2. JBRULES-2667

DroolsSpringJpaManager should use different Entity Managers for CMD and APP.

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    Description

      Just like DefaultJpaManager does, DroolsSpringJpaManager must use different Enitity Managers: one for CMD transactions and another one for APP transactions.
      One of the visible effects of this issue is that flow's timers doesn't run properly using spring.

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBRULES-2599 Timers Do Not Get Triggered when using JPA Knowledge Session

          • 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.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBRULES-2657 DroolsSpringTransactionManager does not join an Existing Spring Transaction

          • 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.
          • Closed

          Activity

            People

              esteban.aliverti@gmail.com Esteban Aliverti (Inactive)
              esteban.aliverti@gmail.com Esteban Aliverti (Inactive)
              Archiver:
              rhn-support-ceverson Clark Everson

              Dates

                Created:
                Updated:
                Resolved:
                Archived:

                PagerDuty