[JBoss JIRA] (AS7-3016) Lazy enlistment of JMS Session does not work - UserTransaction implementation does not support it
6:48 a.m.
Lazy enlistment of JMS Session does not work - UserTransaction implementation does not
support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Jonathan Halliday
Priority: Critical
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:04 p.m.
[
https://issues.jboss.org/browse/AS7-3016?page=com.atlassian.jira.plugin.s...
]
Jiri Pechanec updated AS7-3016:
-------------------------------
Fix Version/s: 7.1.0.CR1
Lazy enlistment of JMS Session does not work - UserTransaction
implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Jonathan Halliday
Priority: Critical
Fix For: 7.1.0.CR1
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:50 a.m.
[
https://issues.jboss.org/browse/AS7-3016?page=com.atlassian.jira.plugin.s...
]
Jonathan Halliday reassigned AS7-3016:
--------------------------------------
Assignee: Stefano Maestri (was: Jonathan Halliday)
Lazy enlistment of JMS Session does not work - UserTransaction
implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Stefano Maestri
Priority: Critical
Fix For: 7.1.0.Final
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:13 a.m.
[
https://issues.jboss.org/browse/AS7-3016?page=com.atlassian.jira.plugin.s...
]
Jesper Pedersen reassigned AS7-3016:
------------------------------------
Assignee: Tom Jenkinson (was: Stefano Maestri)
Tom, JCA uses UserTransactionListener through the UserTransactionRegistry. Should
ServerVMClientUserTransaction be used as the UserTransaction instance - or is there a
better way to do the TX part now ?
Lazy enlistment of JMS Session does not work - UserTransaction
implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Tom Jenkinson
Priority: Critical
Fix For: 7.1.0.Final
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:25 p.m.
[
https://issues.jboss.org/browse/AS7-3016?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas updated AS7-3016:
--------------------------------
Priority: Blocker (was: Critical)
Lazy enlistment of JMS Session does not work - UserTransaction
implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Tom Jenkinson
Priority: Blocker
Fix For: 7.1.0.Final
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9 a.m.
[
https://issues.jboss.org/browse/AS7-3016?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson commented on AS7-3016:
------------------------------------
I can't see why we can't use ServerVMClientUserTransaction, I didn't write the
integration code (org.jboss.as.txn.service.ArjunaTransactionManagerService) and I
don't believe I have access to the test case Jiri raised this with to verify it but I
have built AS7 locally using "ServerVMClientUserTransaction(instance of an arjuna
transaction manager)" and this seems to pass the smoke tests. Looking at the code it
would seem to be safe too.
Would be interested to know why the original code did not use
ServerVMClientUserTransaction. This could possibly be a question for:
* @author <a href="mailto:david.lloyd@redhat.com">David M.
Lloyd</a>
* @author Thomas.Diesler(a)jboss.com
* @author Scott Stark (sstark(a)redhat.com) (C) 2011 Red Hat Inc.
As to what to do to resolve this, as I say I have a patch here (its +2 lines, -2 lines). I
am reluctant to pull request it as I don't really own the integration code - I believe
that is Stefano Maestri - and therefore would prefer Stefano to have the opportunity to
provide some feedback.
Lazy enlistment of JMS Session does not work - UserTransaction
implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Tom Jenkinson
Priority: Blocker
Fix For: 7.1.0.Final
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 a.m.
[
https://issues.jboss.org/browse/AS7-3016?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson updated AS7-3016:
-------------------------------
Attachment: usertransaction.patch
This shows how the usertransaction can be altered. As I mentioned in my comment I am
reluctant to patch this myself as it is not jbossts code per se that is at fault, rather
the transactions integration code in AS7 appears to be electing to use a different
UserTransaction impl and this is not my code so there could be a reason for this.
Lazy enlistment of JMS Session does not work - UserTransaction
implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Tom Jenkinson
Priority: Blocker
Fix For: 7.1.0.Final
Attachments: usertransaction.patch
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:31 a.m.
[
https://issues.jboss.org/browse/AS7-3016?page=com.atlassian.jira.plugin.s...
]
Jesper Pedersen commented on AS7-3016:
--------------------------------------
It is basically a matter of which UserTransaction implementation that should be used. The
internal listener in ServerVMClientUserTransaction is deprecated since the integration
should be done through the UserTransactionRegistry instead. The question is which
implementation on the TX side which supports that construct.
However, we can do
{code}
ServerVMClientUserTransaction usertx = ServerVMClientUserTransaction.getSingleton();
usertx.setUserTransactionRegistry(utrService.getValue());
{code}
for AS 7.1.
For Narayana the best solution is that the SPI lives with the implementation and all
deprecated classes/methods are removed. Or even we design a complete new SPI, that are
more in line with the design of AS7 service architecture.
Lazy enlistment of JMS Session does not work - UserTransaction
implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Tom Jenkinson
Priority: Blocker
Fix For: 7.1.0.Final
Attachments: usertransaction.patch
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:40 a.m.
[
https://issues.jboss.org/browse/AS7-3016?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-3016:
-------------------------------------
I have a commit which fixes the problem at
https://github.com/stuartwdouglas/jboss-as/commit/c0531eac852a2a92f4c740a...
Tomorrow I will clean it up and hopefully get it merged in time for tomorrows TCK run.
Lazy enlistment of JMS Session does not work - UserTransaction
implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Tom Jenkinson
Priority: Blocker
Fix For: 7.1.0.Final
Attachments: usertransaction.patch, userTransactionRegistry.diff
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:18 a.m.
[
https://issues.jboss.org/browse/AS7-3016?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson commented on AS7-3016:
------------------------------------
Great, thanks for taking this on!
Lazy enlistment of JMS Session does not work - UserTransaction
implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Tom Jenkinson
Priority: Blocker
Fix For: 7.1.0.Final
Attachments: usertransaction.patch, userTransactionRegistry.diff
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:24 p.m.
[
https://issues.jboss.org/browse/AS7-3016?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas closed AS7-3016.
-------------------------------
Assignee: Stuart Douglas (was: Tom Jenkinson)
Resolution: Done
This is now resolved. The TX implementation has been changed as per Tom's comment, and
the CachedConnectionManager has been hooked wired up for ejb and web invocations.
Lazy enlistment of JMS Session does not work - UserTransaction
implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Stuart Douglas
Priority: Blocker
Fix For: 7.1.0.Final
Attachments: usertransaction.patch, userTransactionRegistry.diff
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:25 p.m.
[
https://issues.jboss.org/browse/AS7-3016?page=com.atlassian.jira.plugin.s...
]
Doug Grove commented on AS7-3016:
---------------------------------
I have the same issue for CMT and SessionContext. I have to get a QueueSession inside of
the transactional method:
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public void sendMessage() throws JMSException {
Logger.getLogger(SenderBean.class.getName()).log(Level.INFO,
"Entering/Exiting sendMessage");
if (sender == null)
sender = session.createSender(queue);
ObjectMessage msg = session.createObjectMessage("testMsg");
sender.send(msg);
If I create the QueueSession in the beans init() method, then transactions do not
propagate. Is this the same issue? Has this bee addressed?
Thanks much,
Doug
Lazy enlistment of JMS Session does not work - UserTransaction
implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Stuart Douglas
Priority: Blocker
Fix For: 7.1.0.Final
Attachments: usertransaction.patch, userTransactionRegistry.diff
This test case was identified in TCK6. There is a MDB with CMT configured -
com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification
org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which
receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by
org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately
org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes
com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not
have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4428
days inactive
4713
days old
11 comments
11 participants
participants (11)
-
Doug Grove (JIRA) -
Jesper Pedersen (Assigned) (JIRA)
-
Jesper Pedersen (Commented) (JIRA)
-
Jiri Pechanec (Created) (JIRA)
-
Jiri Pechanec (Updated) (JIRA)
-
Jonathan Halliday (Assigned) (JIRA)
-
Stuart Douglas (Closed) (JIRA)
-
Stuart Douglas (Commented) (JIRA)
-
Stuart Douglas (Updated) (JIRA)
-
Tom Jenkinson (Commented) (JIRA)
-
Tom Jenkinson (Updated) (JIRA)