[jira] [Commented] (ARIES-1783) TransactionRequiredException when non-transactional method precedes a transactional one in the same service.

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (ARIES-1783) TransactionRequiredException when non-transactional method precedes a transactional one in the same service.

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/ARIES-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764781#comment-16764781 ]

ASF subversion and git services commented on ARIES-1783:
--------------------------------------------------------

Commit 8f46ae5c58e90832ab8886ab6f5d7c7d9f7fada2 in aries-jpa's branch refs/heads/master from Christian Schneider
[ https://gitbox.apache.org/repos/asf?p=aries-jpa.git;h=8f46ae5 ]

Merge pull request #7 from Smasherr/requires_new_after_never

ARIES-1783 Fix memory leak in EMSupplerImpl

> TransactionRequiredException when non-transactional method precedes a transactional one in the same service.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-1783
>                 URL: https://issues.apache.org/jira/browse/ARIES-1783
>             Project: Aries
>          Issue Type: Bug
>          Components: JPA
>    Affects Versions: jpa-2.5.0
>            Reporter: Daniel Estermann
>            Assignee: Christian Schneider
>            Priority: Major
>             Fix For: jpa-2.7.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Assume I have a service implementation with a method annotated with @Transactional and one of TxTypes not starting a transaction:
>  * NEVER
>  * NOT_SUPPORTED
>  * SUPPORTS
> From that non-transactional method I want to use a self-reference resolved via BundleContext to call a transactional method in the same service, annotated with one of those TxTypes:
>  * REQUIRED
>  * REQURES_NEW
> Since the resolved self-reference is a proxied object I expect it to be able to start a new transaction. This is not the case however and the subject exception occurs.
>  
> I created a test case revealing the issue in the following pull request: https://github.com/apache/aries-jpa/pull/2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)