[JBoss JIRA] (JBTM-1099) WS-BA to 2xJTA bridge
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1099?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1099:
--------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M2)
> WS-BA to 2xJTA bridge
> ---------------------
>
> Key: JBTM-1099
> URL: https://issues.jboss.org/browse/JBTM-1099
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Labels: assign
> Fix For: 5.0.0.Final
>
> Original Estimate: 1 week
> Time Spent: 3 hours
> Remaining Estimate: 4 days, 5 hours
>
> It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated.
> There may be other windows in Compensate and Close. This needs investigating.
> The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close.
> This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common.
--
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, 2 months
[JBoss JIRA] (JBTM-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris logged work on JBTM-1407:
-----------------------------------------
Author: Gytis Trikleris
Created on: 28/Jan/13 1:13 PM
Start Date: 28/Jan/13 5:00 AM
Worklog Time Spent: 4 hours
Issue Time Tracking
-------------------
Remaining Estimate: 1 hour (was: 2 hours)
Time Spent: 3 days, 1 hour, 50 minutes (was: 2 days, 5 hours, 50 minutes)
Worklog Id: (was: 12428508)
> Have a build option that builds JTS only against JacORB or IDLJ, but not both.
> ------------------------------------------------------------------------------
>
> Key: JBTM-1407
> URL: https://issues.jboss.org/browse/JBTM-1407
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 4.17.3
> Reporter: Mark Little
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M2
>
> Time Spent: 3 days, 1 hour, 50 minutes
> Remaining Estimate: 1 hour
>
> This boils down to supporting two new profiles:
> ./build.sh -P jts-jacorb
> ./build.sh -P jts-idlj
--
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, 2 months
[JBoss JIRA] (JBTM-1424) Remove static block from org.jboss.jbossts.xts.environment.XTSPropertyManager
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1424?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1424:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Remove static block from org.jboss.jbossts.xts.environment.XTSPropertyManager
> -----------------------------------------------------------------------------
>
> Key: JBTM-1424
> URL: https://issues.jboss.org/browse/JBTM-1424
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M2
>
> Original Estimate: 10 minutes
> Time Spent: 10 minutes
> Remaining Estimate: 0 minutes
>
> Where it catches an exception in the static block and then just uses system properties. I would say that behavior would be better encapsulated in XTSPropertiesFactory.getDefaultProperties itself (thereby removing another static block and making XTSPropertiesFactory.getDefaultProperties more stable).
--
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, 2 months
[JBoss JIRA] (JBTM-1099) WS-BA to 2xJTA bridge
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1099?page=com.atlassian.jira.plugin.... ]
Paul Robinson logged work on JBTM-1099:
---------------------------------------
Author: Paul Robinson
Created on: 25/Jan/13 10:06 AM
Start Date: 25/Jan/13 10:06 AM
Worklog Time Spent: 3 hours
Issue Time Tracking
-------------------
Remaining Estimate: 4 days, 5 hours (was: 1 week)
Time Spent: 3 hours
Worklog Id: (was: 12428506)
> WS-BA to 2xJTA bridge
> ---------------------
>
> Key: JBTM-1099
> URL: https://issues.jboss.org/browse/JBTM-1099
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Labels: assign
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 week
> Time Spent: 3 hours
> Remaining Estimate: 4 days, 5 hours
>
> It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated.
> There may be other windows in Compensate and Close. This needs investigating.
> The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close.
> This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common.
--
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, 2 months