[jboss-jira] [JBoss JIRA] (AS7-6586) JPA afterCompletion sync may be called from non-application thread, resolve concurrency concern

[Scott Marlow (JIRA)]

     [ https://issues.jboss.org/browse/AS7-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Marlow updated AS7-6586:
------------------------------

    Fix Version/s: 8.0.0.Alpha1
      Description: 
For transaction scoped entity managers, the closing the of entity manager is deferred until after the transaction completes.

It is possible that the transaction manager/service may call the Transaction sync from a non-application thread (tx timeout reaper thread or normal completion in remote propagated tx case).  Guards need to be added to make sure that a tx timeout, doesn't interfere with normal application usage of the entity manager.

  was:
For transaction scoped entity managers, the closing the of entity manager is deferred until after the transaction completes.




    
> JPA afterCompletion sync may be called from non-application thread, resolve concurrency concern
> -----------------------------------------------------------------------------------------------
>
>                 Key: AS7-6586
>                 URL: https://issues.jboss.org/browse/AS7-6586
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: JPA / Hibernate
>    Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP)
>            Reporter: Scott Marlow
>            Assignee: Scott Marlow
>             Fix For: 8.0.0.Alpha1
>
>
> For transaction scoped entity managers, the closing the of entity manager is deferred until after the transaction completes.
> It is possible that the transaction manager/service may call the Transaction sync from a non-application thread (tx timeout reaper thread or normal completion in remote propagated tx case).  Guards need to be added to make sure that a tx timeout, doesn't interfere with normal application usage of the entity manager.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira