[jboss-jira] [JBoss JIRA] (WFLY-3548) JTA synchronization for a distributed transaction called with incorrect TCCL
[
https://issues.jboss.org/browse/WFLY-3548?page=com.atlassian.jira.plugin....
]
Martin Kouba commented on WFLY-3548:
------------------------------------
One way is described in the referenced [bugzilla
issue|https://bugzilla.redhat.com/show_bug.cgi?id=1098127 ].
The other way is a bit simpler:
# Enable JTS
# Run CDI TCK test:
{{org.jboss.cdi.tck.tests.event.observer.transactional.TransactionalObserverTest}} - note
that this test is currently missing some assertions (CDITCK-427) and does not fail,
however you should see exceptions in the log
## git clone git@github.com:weld/core.git
## cd core/jboss-tck-runner/1.1/
## mvn clean test -Dincontainer
-DtckTest=TransactionalObserverTest#testSucessfullTransaction
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)