March 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1505) WS-BA transaction context not propagated if JTA transaction present.

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1505?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1505: -------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > WS-BA transaction context not propagated if JTA transaction present. > -------------------------------------------------------------------- > > Key: JBTM-1505 > URL: https://issues.jboss.org/browse/JBTM-1505 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > With default-context-propagation enabled: > What happens if the Client is running in a JTA transaction, then begins a WS-BA transaction before calling a WS-BA enabled service? I suspect, as it stands, we would start a WS-AT transaction as well. This will cause the JaxBaseHeaderContextProcessor to default to WS-AT as it appears first in the if-then-elseif block: > {code} > final CoordinationContextType coordinationContext ; > if (atContext != null) > { > coordinationContext = atContext.getCoordinationContext() ; > } > else if (baContext != null) > { > coordinationContext = baContext.getCoordinationContext() ; > } > {code} > I'm not yet sure how we handle this case. We certainly need a test for it though. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1472) Initial work on JTA for Compensations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1472?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1472: -------------------------------- Description: We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market. This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API. was: We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market. > Initial work on JTA for Compensations > ------------------------------------- > > Key: JBTM-1472 > URL: https://issues.jboss.org/browse/JBTM-1472 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > > We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). > It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market. > This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1472) Initial work on JTA for Compensations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1472?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1472: -------------------------------- Summary: Initial work on JTA for Compensations (was: JTA for Compensations) > Initial work on JTA for Compensations > ------------------------------------- > > Key: JBTM-1472 > URL: https://issues.jboss.org/browse/JBTM-1472 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > > We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). > It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1106) @Transactional like support for BA

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1106?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1106: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M3) > @Transactional like support for BA > ---------------------------------- > > Key: JBTM-1106 > URL: https://issues.jboss.org/browse/JBTM-1106 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 5.0.0.Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Allow a WS-BA transaction to be started from a CDI enabled bean using EJB TX annotation like interceptors. We should copy what is proposed for http://java.net/jira/browse/JTA_SPEC-5 for consistency's sake. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1106) @Transactional like support for BA

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1106?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1106: ------------------------------------- May be folded into JBTM-1472 or obsoleted by it. I won't know until I've given JBTM-1472 some thought. > @Transactional like support for BA > ---------------------------------- > > Key: JBTM-1106 > URL: https://issues.jboss.org/browse/JBTM-1106 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 5.0.0.Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Allow a WS-BA transaction to be started from a CDI enabled bean using EJB TX annotation like interceptors. We should copy what is proposed for http://java.net/jira/browse/JTA_SPEC-5 for consistency's sake. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1344) org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins)

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1344?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1344: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M3) > org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins) > ------------------------------------------------------------------------------------ > > Key: JBTM-1344 > URL: https://issues.jboss.org/browse/JBTM-1344 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TxBridge > Affects Versions: 4.17.3 > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 4.17.4, 5.0.0.Final > > Original Estimate: 2 days > Time Spent: 1 hour, 30 minutes > Remaining Estimate: 1 day, 6 hours, 30 minutes > > See: http://172.17.131.2/job/jbossts-narayana-java6/81/ -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1468) Support pure-JTA client and server for WS-AT and REST-AT

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1468?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1468: -------------------------------- Assignee: Paul Robinson > Support pure-JTA client and server for WS-AT and REST-AT > -------------------------------------------------------- > > Key: JBTM-1468 > URL: https://issues.jboss.org/browse/JBTM-1468 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > > This allows the Client and server application to just use the JTA APIs, whilst having the distribution done over WS-AT or REST-AT. > To do this we need to: > # Remove @Transactional annotation. We then need to use some other mechanism to support the (optional) WS-AT participants that want to use annotations. > # Client side JTA->REST-AT bridge. Needs implementing. > # Server side REST-AT->JTA bridge. Needs integrating into code base. > # Update the TXBridge quickstarts to use this and move them out. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1475) TXBridge InboundCrashRecoveryTests failure - could not start container

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1475?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1475: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M3) > TXBridge InboundCrashRecoveryTests failure - could not start container > ---------------------------------------------------------------------- > > Key: JBTM-1475 > URL: https://issues.jboss.org/browse/JBTM-1475 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.Final > > > See: http://172.17.131.2/job/narayana-dualstack/83 > {noformat} > Tests in error: > testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Could not start container > testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Deployment with name txbridge-inbound-tests-client could not be undeployed. Container jboss must be still running. > {noformat} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1468) Support pure-JTA client and server for WS-AT and REST-AT

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1468?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1468: -------------------------------- Original Estimate: 2 days Remaining Estimate: 2 days > Support pure-JTA client and server for WS-AT and REST-AT > -------------------------------------------------------- > > Key: JBTM-1468 > URL: https://issues.jboss.org/browse/JBTM-1468 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > This allows the Client and server application to just use the JTA APIs, whilst having the distribution done over WS-AT or REST-AT. > To do this we need to: > # Remove @Transactional annotation. We then need to use some other mechanism to support the (optional) WS-AT participants that want to use annotations. > # Client side JTA->REST-AT bridge. Needs implementing. > # Server side REST-AT->JTA bridge. Needs integrating into code base. > # Update the TXBridge quickstarts to use this and move them out. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1494) Produce performance figures to show improvement of using WS-BA over WAN

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1494?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1494: -------------------------------- Original Estimate: 3 days Remaining Estimate: 3 days Description: As part of evangelising compensations, it would be useful to show the performance comparisons for an application distributed over the internet. Ideally, these results should show that that the performance of WS-BA is a lot better than WS-AT. Also it would be good to show that the overhead of using WS-BA over not using it, is relatively small compared to the benefits of guarantees it gives. We might need to spend some time doing some minor optimizations as part of this issue. was: As part of evangelising compensations, it would be useful to show the performance comparisons for an application distributed over the internet. Ideally, these results should show that that the performance of WS-BA is a lot better than WS-AT. Also it would be good to show that the overhead of using WS-BA over not using it, is relatively small compared to the benefits of guarantees it gives. > Produce performance figures to show improvement of using WS-BA over WAN > ----------------------------------------------------------------------- > > Key: JBTM-1494 > URL: https://issues.jboss.org/browse/JBTM-1494 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Fix For: 5.0.0.M3 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > As part of evangelising compensations, it would be useful to show the performance comparisons for an application distributed over the internet. > Ideally, these results should show that that the performance of WS-BA is a lot better than WS-AT. Also it would be good to show that the overhead of using WS-BA over not using it, is relatively small compared to the benefits of guarantees it gives. > We might need to spend some time doing some minor optimizations as part of this issue. -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2013