[jboss-jira] [JBoss JIRA] Commented: (JBRULES-2667) DroolsSpringJpaManager should use different Entity Managers for CMD and APP.

[Anatoly Polinsky (JIRA)]

    [ https://jira.jboss.org/browse/JBRULES-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12554704#action_12554704 ] 

Anatoly Polinsky commented on JBRULES-2667:
-------------------------------------------

This is NOT a solution for Timers to work. Timers do not work when using persistence ( JPA ) anyway with or without this "fix".

But what it does do, it causes confusions ( within Drools codebase itself ) and issues: https://jira.jboss.org/browse/JBRULES-2717

/Anatoly

> DroolsSpringJpaManager should use different Entity Managers for CMD and APP.
> ----------------------------------------------------------------------------
>
>                 Key: JBRULES-2667
>                 URL: https://jira.jboss.org/browse/JBRULES-2667
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.1.0.FINAL
>            Reporter: Esteban Aliverti
>            Assignee: Esteban Aliverti
>             Fix For: 5.1.1.FINAL
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira