[JBoss JIRA] (JBTM-1753) Merge TXFramework and CompensationsAPI-prototype
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1753:
-----------------------------------
Summary: Merge TXFramework and CompensationsAPI-prototype
Key: JBTM-1753
URL: https://issues.jboss.org/browse/JBTM-1753
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: TXFramework
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M4
The current implementation of the compensations API was a quick prototype I knocked up ready for JUDCon. It needs merging into the existing TXFramework API.
This will need some investigation as there are now multiple ways of doing the same thing. We need to decide which or both to keep.
--
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, 7 months
[JBoss JIRA] (JBTM-1680) Allow 2PC participants to enlist in a compensation-based transaction
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1680?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1680:
-------------------------------------
Possible use-case: Having a MongoDB instance participate a transaction with XA resources.
> Allow 2PC participants to enlist in a compensation-based transaction
> --------------------------------------------------------------------
>
> Key: JBTM-1680
> URL: https://issues.jboss.org/browse/JBTM-1680
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M4
>
>
> In some situations a developer may need to coordinate multiple resources, where some are 2PC and some are not. Here it could be possible to use enlist the 2PC participants in a compensation-based transaction. The xa.prepare happens in the complete phase, the xa.commit during close and xa.rollback during compensate.
> This could provide an alternative to LRCO, where the last resource is compensation-based and the other resources remain 2PC. The benefit of this approach is that the failure window associated with LRCO does not exist. The negative of this approach is that the isolation of the compensation-based participant is reduced.
--
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, 7 months
[JBoss JIRA] (JBTM-1680) Allow 2PC participants to enlist in a compensation-based transaction
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1680?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1680:
--------------------------------
Fix Version/s: 5.0.0.M4
(was: 5.0.0.Final)
> Allow 2PC participants to enlist in a compensation-based transaction
> --------------------------------------------------------------------
>
> Key: JBTM-1680
> URL: https://issues.jboss.org/browse/JBTM-1680
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M4
>
>
> In some situations a developer may need to coordinate multiple resources, where some are 2PC and some are not. Here it could be possible to use enlist the 2PC participants in a compensation-based transaction. The xa.prepare happens in the complete phase, the xa.commit during close and xa.rollback during compensate.
> This could provide an alternative to LRCO, where the last resource is compensation-based and the other resources remain 2PC. The benefit of this approach is that the failure window associated with LRCO does not exist. The negative of this approach is that the isolation of the compensation-based participant is reduced.
--
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, 7 months
[JBoss JIRA] (JBTM-1680) Allow 2PC participants to enlist in a compensation-based transaction
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1680?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1680:
--------------------------------
Priority: Minor (was: Major)
> Allow 2PC participants to enlist in a compensation-based transaction
> --------------------------------------------------------------------
>
> Key: JBTM-1680
> URL: https://issues.jboss.org/browse/JBTM-1680
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> In some situations a developer may need to coordinate multiple resources, where some are 2PC and some are not. Here it could be possible to use enlist the 2PC participants in a compensation-based transaction. The xa.prepare happens in the complete phase, the xa.commit during close and xa.rollback during compensate.
> This could provide an alternative to LRCO, where the last resource is compensation-based and the other resources remain 2PC. The benefit of this approach is that the failure window associated with LRCO does not exist. The negative of this approach is that the isolation of the compensation-based participant is reduced.
--
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, 7 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 updated JBTM-1645:
--------------------------------
Fix Version/s: 5.0.0.M4
(was: 5.0.0.Final)
> 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: Paul Robinson
> Fix For: 5.0.0.M4
>
> 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, 7 months
[JBoss JIRA] (JBTM-1678) JTA 1.2 @Transactional for compensations
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1678?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1678:
--------------------------------
Original Estimate: (was: 2 days)
Remaining Estimate: (was: 2 days)
Assignee: Gytis Trikleris (was: Paul Robinson)
> JTA 1.2 @Transactional for compensations
> ----------------------------------------
>
> Key: JBTM-1678
> URL: https://issues.jboss.org/browse/JBTM-1678
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework, XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> Essentially offer comparable features for Compensations as those defined for JTA in the @Transactional section of the JTA spec.
> We can re-use the code and tests from our JTA 1.2 implementation. It may be possible to extend those impls, otherwise it's a copy-and-paste.
--
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, 7 months
[JBoss JIRA] (JBTM-1678) JTA 1.2 @Transactional for compensations
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1678?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1678:
--------------------------------
Priority: Major (was: Minor)
> JTA 1.2 @Transactional for compensations
> ----------------------------------------
>
> Key: JBTM-1678
> URL: https://issues.jboss.org/browse/JBTM-1678
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework, XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M4
>
>
> Essentially offer comparable features for Compensations as those defined for JTA in the @Transactional section of the JTA spec.
> We can re-use the code and tests from our JTA 1.2 implementation. It may be possible to extend those impls, otherwise it's a copy-and-paste.
--
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, 7 months
[JBoss JIRA] (JBTM-1678) JTA 1.2 @Transactional for compensations
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1678?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1678:
--------------------------------
Description:
Essentially offer comparable features for Compensations as those defined for JTA in the @Transactional section of the JTA spec.
We can re-use the code and tests from our JTA 1.2 implementation. It may be possible to extend those impls, otherwise it's a copy-and-paste.
was:Essentially offer comparable features for Compensations as those defined for JTA in the @Transactional section of the JTA spec.
> JTA 1.2 @Transactional for compensations
> ----------------------------------------
>
> Key: JBTM-1678
> URL: https://issues.jboss.org/browse/JBTM-1678
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> Essentially offer comparable features for Compensations as those defined for JTA in the @Transactional section of the JTA spec.
> We can re-use the code and tests from our JTA 1.2 implementation. It may be possible to extend those impls, otherwise it's a copy-and-paste.
--
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, 7 months