Bug 1032932 - TransactionMixIn misconfigures TransactionSynchronizationRegistry
Summary: TransactionMixIn misconfigures TransactionSynchronizationRegistry
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: SwitchYard
Version: 6.0.0
Hardware: All
OS: All
unspecified
unspecified
Target Milestone: DR1
: 6.1.0
Assignee: Tomohisa Igarashi
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-21 09:26 UTC by Daniel Tschan, Puzzle ITC
Modified: 2025-02-10 03:34 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:34:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Unit test demonstrating the problem. (1.17 KB, text/plain)
2013-11-21 09:26 UTC, Daniel Tschan, Puzzle ITC
no flags Details
Proposed patch for the issue. (2.89 KB, patch)
2013-11-21 11:44 UTC, Daniel Tschan, Puzzle ITC
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SWITCHYARD-1860 0 Major Resolved TransactionSynchronizationRegistry doesn't work on TransactionMixIn 2018-12-20 10:46:41 UTC

Description Daniel Tschan, Puzzle ITC 2013-11-21 09:26:46 UTC
Created attachment 827091 [details]
Unit test demonstrating the problem.

Description of problem:
The TransactionMixIn class doesn't configure the JTAEnvironmentBean used by the TransactionSynchronizationRegistry it registers in JNDI. As soon as the TransactionSynchronizationRegistry is used directly or indirectly an exception is thrown and the test is aborted.


Version-Release number of selected component (if applicable):
JBoss Fuse Service Works 6.0.0 Beta

How reproducible:
Always, see attached unit test.

Steps to Reproduce:
1. Run attached unit test.
2.
3.

Actual results:

Test aborts with:
com.arjuna.ats.arjuna.exceptions.FatalError
	at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:87)
	at com.arjuna.ats.internal.jts.OTSImpleManager.<clinit>(OTSImpleManager.java:296)
	at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.getTransaction(TransactionImple.java:1126)
	at com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction.getStatus(BaseTransaction.java:195)
	at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.getTransactionStatus(TransactionSynchronizationRegistryImple.java:161)
	at ch.bls.schub.infrastructure.persistence.TransactionSynchronizationRegistryTest.testTransactionSynchronizationRegistry(TransactionSynchronizationRegistryTest.java:21)


additionally the following error is logged:

09:55:10,443 FATAL [com.arjuna.ats.jts] ARJUNA022006: The ORB has not been initialized yet



Expected results:
TransactionSynchronizationRegistry works as described by JTA spec.

Additional info:
Proposed patch to follow.

Comment 2 Daniel Tschan, Puzzle ITC 2013-11-21 11:44:24 UTC
Created attachment 827153 [details]
Proposed patch for the issue.

Comment 3 Keith Babo 2013-11-21 15:14:21 UTC
Thanks for reporting the issue and the providing a patch.  Tomo - can you have a look at this?

Setting devel ack to '-' due to the fact that this is not a blocker for 6.0.

Comment 4 Tomohisa Igarashi 2013-11-22 10:18:05 UTC
Confirmed the problem and the suggested fix avoid it. A pull request is linked to SWITCHYARD-1860 so we can merge it. Thanks for the report, tschan!

Comment 10 Red Hat Bugzilla 2025-02-10 03:34:26 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.