[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.Final
(was: 5.0.0.M5)
> 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.Final
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> 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
12 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:
-------------------------------------
Pushing to 5.0.0.Final. Will pull forward if the MongoDB work needs it.
> 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.M5
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> 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
12 years, 7 months
[JBoss JIRA] (JBTM-1859) Remove classname Strings from XTS subsystem
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1859?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1859:
--------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M5)
> Remove classname Strings from XTS subsystem
> -------------------------------------------
>
> Key: JBTM-1859
> URL: https://issues.jboss.org/browse/JBTM-1859
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Application Server Integration, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.Final
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> THe XTS SubSystem has many classnames passed to Jandex as raw Strings. It would be better to use Class#getName as it is type-safe.
> When this code was written, this was not possible, due to the nature of the order in which class-loading was done and the fact that the code in question was executed very early in the server boot. I don't remember the specific details.
> However, something seems to have changed in WildFly, such that we can now use Class#getName on the classes we require. This issue it to replace all the classname Strings with Class#getName() and to also simplify the code under org.jboss.as.xts.jandex, as a lot of that verbose code was added to to cope with the limitation of not being able to use Class#getName().
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1705) Remove XTS CDI Extension
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1705?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1705:
--------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M5)
> Remove XTS CDI Extension
> ------------------------
>
> Key: JBTM-1705
> URL: https://issues.jboss.org/browse/JBTM-1705
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.Final
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> WFLY-1370 removes the need for the CDIExtensionProcessor in the XTS subsytem.
> There is currently a hack in CDIExtensionProcessor in 5_BRANCH. This MUST be removed if WFLY-1370 is not merged in time for release. Hence I have marked this as critical.
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1859) Remove classname Strings from XTS subsystem
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1859?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1859:
--------------------------------
Priority: Minor (was: Major)
> Remove classname Strings from XTS subsystem
> -------------------------------------------
>
> Key: JBTM-1859
> URL: https://issues.jboss.org/browse/JBTM-1859
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Application Server Integration, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M5
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> THe XTS SubSystem has many classnames passed to Jandex as raw Strings. It would be better to use Class#getName as it is type-safe.
> When this code was written, this was not possible, due to the nature of the order in which class-loading was done and the fact that the code in question was executed very early in the server boot. I don't remember the specific details.
> However, something seems to have changed in WildFly, such that we can now use Class#getName on the classes we require. This issue it to replace all the classname Strings with Class#getName() and to also simplify the code under org.jboss.as.xts.jandex, as a lot of that verbose code was added to to cope with the limitation of not being able to use Class#getName().
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1705) Remove CDIExtensionProcessor in the XTS subsytem
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1705?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1705:
--------------------------------
Summary: Remove CDIExtensionProcessor in the XTS subsytem (was: Remove XTS CDI Extension)
> Remove CDIExtensionProcessor in the XTS subsytem
> ------------------------------------------------
>
> Key: JBTM-1705
> URL: https://issues.jboss.org/browse/JBTM-1705
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.Final
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> WFLY-1370 removes the need for the CDIExtensionProcessor in the XTS subsytem.
> There is currently a hack in CDIExtensionProcessor in 5_BRANCH. This MUST be removed if WFLY-1370 is not merged in time for release. Hence I have marked this as critical.
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1705) Remove XTS CDI Extension
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1705?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1705:
--------------------------------
Priority: Minor (was: Critical)
> Remove XTS CDI Extension
> ------------------------
>
> Key: JBTM-1705
> URL: https://issues.jboss.org/browse/JBTM-1705
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M5
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> WFLY-1370 removes the need for the CDIExtensionProcessor in the XTS subsytem.
> There is currently a hack in CDIExtensionProcessor in 5_BRANCH. This MUST be removed if WFLY-1370 is not merged in time for release. Hence I have marked this as critical.
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1705) Remove XTS CDI Extension
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1705?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1705:
-------------------------------------
Lowering to minor as WFLY-1370 was merged in time.
> Remove XTS CDI Extension
> ------------------------
>
> Key: JBTM-1705
> URL: https://issues.jboss.org/browse/JBTM-1705
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M5
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> WFLY-1370 removes the need for the CDIExtensionProcessor in the XTS subsytem.
> There is currently a hack in CDIExtensionProcessor in 5_BRANCH. This MUST be removed if WFLY-1370 is not merged in time for release. Hence I have marked this as critical.
--
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
12 years, 7 months
[JBoss JIRA] (JBTM-1752) Investigate usage of Compensations API with MongoDB
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1752?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1752:
--------------------------------
Priority: Critical (was: Major)
> Investigate usage of Compensations API with MongoDB
> ---------------------------------------------------
>
> Key: JBTM-1752
> URL: https://issues.jboss.org/browse/JBTM-1752
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M5
>
> Original Estimate: 2 weeks
> Remaining Estimate: 2 weeks
>
> Investigate how people are currently involving a MongoDB server with other resources.
> Investigate wether MongoDB could be enlisted as a compensation-based participant with other XA resources enlisted as 2PC resources.
--
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
12 years, 7 months