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

RH Bugzilla Integration (JIRA) issues at jboss.org
Wed Jul 16 04:22:29 EDT 2014


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

RH Bugzilla Integration commented on WFLY-3548:
-----------------------------------------------

Gytis Trikleris <gtrikler at redhat.com> changed the Status of [bug 1098127|https://bugzilla.redhat.com/show_bug.cgi?id=1098127] from NEW to ASSIGNED

> 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
>      Security Level: Public(Everyone can see) 
>          Components: Transactions
>    Affects Versions: 8.1.0.Final
>            Reporter: Martin Kouba
>            Assignee: Gytis Trikleris
>
> 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.2.6#6264)


More information about the jboss-jira mailing list