[JBoss JIRA] (JBTM-809) Replace transactional driver with ironjacamar
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson updated JBTM-809:
-------------------------------
Fix Version/s: 6.0.0.Final
(was: 5.0.0.Final)
> Replace transactional driver with ironjacamar
> ---------------------------------------------
>
> Key: JBTM-809
> URL: https://issues.jboss.org/browse/JBTM-809
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Resource Manager
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 6.0.0.Final
>
>
> Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server.
> There are several bugs open against transactional driver that will be resolved by completing this work.
> The general approach would be along the lines of:
> Startup
> ======
> Embedded embedded = EmbeddedFactory.create();
> embedded.startup();
> embedded.deploy(new File("my-rar.rar").toURI().toURL());
> embedded.deploy(new File("my-ds.xml").toURI().toURL());
> In use
> =====
> InitialContext initialContext = new InitialContext();
> UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction");
> DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS");
> Shutdown
> =======
> embedded.undeploy(new File("my-ds.xml").toURI().toURL());
> embedded.undeploy(new File("my-rar.rar").toURI().toURL());
> embedded.shutdown(); // does not work - some threads don't stop
> Problems?
> =========
> JCA transitive dependencies?
> Accessing ds files from war?
> Accessing rar from war?
> May have to provide these both upfront.
--
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
11 years, 4 months
[JBoss JIRA] (JBTM-1890) SimpleIsolatedServers CI test failures
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1890?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1890:
--------------------------------
Fix Version/s: 4.17.9
5.0.0.M5
> SimpleIsolatedServers CI test failures
> --------------------------------------
>
> Key: JBTM-1890
> URL: https://issues.jboss.org/browse/JBTM-1890
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 4.17.7
> Reporter: Michael Musgrove
> Assignee: Tom Jenkinson
> Fix For: 4.17.9, 5.0.0.M5
>
>
> Various failures in SimpleIsolatedServers tests:
> testTransactionReaperIsCleanedUp failed with
> java.lang.IllegalStateException: ARJUNA016063: The transaction is not active!
> testTwoPhaseXAResourceOrphan
> testOnePhaseXAResourceOrphan
> testOnePhaseSubordinateOrphan
> testRecovery
> java.lang.AssertionError: Servers were not aborted
> testOnePhaseCommit
> java.lang.NullPointerException
> at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.stop(RecoveryManagerService.java:73)
--
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
11 years, 4 months
[JBoss JIRA] (JBTM-1718) Resolve the ParticipantCompletion race condition
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1718?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1718:
----------------------------------
Fix Version/s: 6.0.0.Final
(was: 5.0.0.M5)
> Resolve the ParticipantCompletion race condition
> ------------------------------------------------
>
> Key: JBTM-1718
> URL: https://issues.jboss.org/browse/JBTM-1718
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Fix For: 6.0.0.Final
>
>
> This issue is documented here: JBTM-1429
> In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a distributed environment. This is true, however, the Compensations API is designed to work local-only as well as distributed over WS-BA. Therefore it is much more likely to happen in a production environment.
> Therefore we need to remove this race condition. It can be done in a proprietary mannor as we are not interoperating with another implementation ion local-only mode. When distributing the transaction we fall back to the standard protocol that is susceptible to the race condition. However, as we stated in the docs, this condition is unlikely to manifest in a distributed environment.
--
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
11 years, 4 months
[JBoss JIRA] (JBTM-1645) Allow pull requests to configure some parameters in scripts/hudson/narayana.sh
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1645?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-1645:
---------------------------------------
I've added following options: !MAIN, !XTS, !RTS, !BLACKTIE, !QA_JTS_JACORB, !QA_JTS_JDKORB
> Allow pull requests to configure some parameters in scripts/hudson/narayana.sh
> ------------------------------------------------------------------------------
>
> Key: JBTM-1645
> URL: https://issues.jboss.org/browse/JBTM-1645
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M5
>
> Original Estimate: 4 hours
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> If the pull description has something like this:
> export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=1 TXF_TESTS=1 XTS_TESTS=1 XTS_AS_TESTS=1 txbridge=1 QA_TESTS=1 [SUN_ORB=0] [JAC_ORB=1] [QA_TARGET=ci-jts-tests]
> We could use it in scripts/hudson/narayana.sh if we detect it is a pull build. We might need to white list users we apply this to.
--
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
11 years, 4 months
[JBoss JIRA] (JBTM-1645) Allow pull requests to configure some parameters in scripts/hudson/narayana.sh
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1645?focusedWorklogId=12429600&page=... ]
Gytis Trikleris logged work on JBTM-1645:
-----------------------------------------
Author: Gytis Trikleris
Created on: 28/Aug/13 6:49 AM
Start Date: 28/Aug/13 6:49 AM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 4 hours)
Time Spent: 1 hour
Worklog Id: (was: 12429600)
> Allow pull requests to configure some parameters in scripts/hudson/narayana.sh
> ------------------------------------------------------------------------------
>
> Key: JBTM-1645
> URL: https://issues.jboss.org/browse/JBTM-1645
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M5
>
> Original Estimate: 4 hours
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> If the pull description has something like this:
> export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=1 TXF_TESTS=1 XTS_TESTS=1 XTS_AS_TESTS=1 txbridge=1 QA_TESTS=1 [SUN_ORB=0] [JAC_ORB=1] [QA_TARGET=ci-jts-tests]
> We could use it in scripts/hudson/narayana.sh if we detect it is a pull build. We might need to white list users we apply this to.
--
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
11 years, 4 months
[JBoss JIRA] (JBTM-1645) Allow pull requests to configure some parameters in scripts/hudson/narayana.sh
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1645?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1645:
-------------------------------------
Note: we only run one set of Orb tests now and we now have BlackTie to consider.
> Allow pull requests to configure some parameters in scripts/hudson/narayana.sh
> ------------------------------------------------------------------------------
>
> Key: JBTM-1645
> URL: https://issues.jboss.org/browse/JBTM-1645
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M5
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> If the pull description has something like this:
> export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=1 TXF_TESTS=1 XTS_TESTS=1 XTS_AS_TESTS=1 txbridge=1 QA_TESTS=1 [SUN_ORB=0] [JAC_ORB=1] [QA_TARGET=ci-jts-tests]
> We could use it in scripts/hudson/narayana.sh if we detect it is a pull build. We might need to white list users we apply this to.
--
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
11 years, 4 months