[jboss-jira] [JBoss JIRA] (WFLY-3548) JTA synchronization for a distributed transaction called with incorrect TCCL

[Martin Kouba (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023617#comment-13023617 ] 

Martin Kouba commented on WFLY-3548:
------------------------------------

The {{NameNotFoundException}} is gone and the CDI TCK test is passing. Waiting for the verification of the second part of the issue (TCCL).

> JTA synchronization for a distributed transaction called with incorrect TCCL
> ----------------------------------------------------------------------------
>
>                 Key: WFLY-3548
>                 URL: https://issues.jboss.org/browse/WFLY-3548
>             Project: WildFly
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 8.1.0.Final
>            Reporter: Martin Kouba
>            Assignee: Martin Kouba
>
> It seems the RequestProcessor which is processing JTA synchronizations
> does not have the right TCCL set.
> As a result, during synchronization invocation:
> * {{NameNotFoundException}} is thrown for a JNDI lookup of "java:comp/UserTransaction"
> * if we try to acccess {{org.jboss.weld.Container}} by means of {{org.jboss.as.weld.services.ModuleGroupSingletonProvider.TCCLSingleton}}, we get ISE: "Singleton not set....This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment."



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)