August 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-974) Allow callback invocation for multiple business method invocations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-974?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-974: ------------------------------- Summary: Allow callback invocation for multiple business method invocations (was: Allow single lifecycle invocation for multiple ServiceRequest invocations) > Allow callback invocation for multiple business method invocations > ------------------------------------------------------------------ > > Key: JBTM-974 > URL: https://issues.jboss.org/browse/JBTM-974 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Labels: TXFramework > Fix For: 5.0.0.Final > > > By setting the 'single' attribute on a Lifecycle Handler Annotation (such as @Prepare or @Compensate) identifies whether more than one callback can be registered for the lifecycle method in response to multiple invocations of the ServiceRequest method. If it is true then the lifecycle method will be called once to the ServiceRequest method. If it is false then the lifecycle method will be called once in response to each (non-read only) call to the ServiceRequest method. The default is 'false'. > Annotation: > {code} > @Retention(RetentionPolicy.RUNTIME) > @Target(ElementType.METHOD) > public @interface Compensate > { > public boolean single() default false; > } > {code} > Example: > {code} > @ServiceRequest > public void addToBasket() > { > //Add another item to the basket. > } > @Compensate(single=true) > public void emptyBasket() > { > //Empty every item from the basket > } > {code} > In this example the @ServiceRequest may be invoked many times to add many items to the basket. The @Compensate method is only needed to be invoked once as the basket can be emptied in one operation. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1444) Review the logging in XTS when WS-AT participants throw Exceptions in commit or rollback

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1444?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1444: -------------------------------- Priority: Minor (was: Major) > Review the logging in XTS when WS-AT participants throw Exceptions in commit or rollback > ---------------------------------------------------------------------------------------- > > Key: JBTM-1444 > URL: https://issues.jboss.org/browse/JBTM-1444 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 5.0.0.Final > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Check what happens when each possible Exception is thrown from a WS-AT participant's commit or Rollback method. > For each case consider whether enough logging is provided. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1515) Investigate the overhead of bridging JTA to WS-AT when not needed

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1515?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1515: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Investigate the overhead of bridging JTA to WS-AT when not needed > ----------------------------------------------------------------- > > Key: JBTM-1515 > URL: https://issues.jboss.org/browse/JBTM-1515 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Fix For: 6.0.0.Final > > > When using default context propagation, a subordinate WS-AT transaction will be created for Web service calls made within a JTA transaction. This is wasteful if the target service does not enlist any participants in this transaction. > We should measure the overhead that this imposes and take steps to reduce/remove it. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1467) Create a set of Koans for using Compensations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1467?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1467: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Create a set of Koans for using Compensations > --------------------------------------------- > > Key: JBTM-1467 > URL: https://issues.jboss.org/browse/JBTM-1467 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Fix For: 6.0.0.Final > > > In the spirit of http://rubykoans.com/, but to learn how to use compensations. > In the long term we should use a Java EE Koan 'runner'. In the short term, try using Arquillian with some broken tests. We could do something to intercept logs for an appropriate error message to present the user. > Might also be worth having Arquillian stop on a failed test to prevent too many failures swamping the user. -- 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, 4 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: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > 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 > Priority: Minor > Fix For: 6.0.0.Final > > 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1507) Review the TXBridge tests usage of Arquillian

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1507?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1507: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Review the TXBridge tests usage of Arquillian > --------------------------------------------- > > Key: JBTM-1507 > URL: https://issues.jboss.org/browse/JBTM-1507 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Testing, TxBridge > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 6.0.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > The TXBridge tests don;t seem to be using Arquillian correctly. There is a servlet that is invoked to do things inside the container. As the tests (should) now run in the container, this should not be needed. > The tests also seem to have added complexity due to the recovery tests. As the recovery tests need to be able to kill the container, it mandates manual container lifecycle management for *all* tests. We may want to pull out the recovery tests into a separate module. > We also may want to pull out the DisabledContextPropagationTest into a separate module as they use a modified AS configuration. > We should also take a general look at how the tests are structured and using Arq. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1422) Deployment failure because of missing service dependencies

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1422?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1422. --------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) Resolution: Out of Date This only happened once and it's not happened in over 7 months. > Deployment failure because of missing service dependencies > ---------------------------------------------------------- > > Key: JBTM-1422 > URL: https://issues.jboss.org/browse/JBTM-1422 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M5 > > > See: http://172.17.131.2/job/narayana/141 > {noformat} > org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase Time elapsed: 16103 sec <<< ERROR! > org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: wsba-participant-completion.war > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83) > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64) > ... > Caused by: java.lang.Exception: { > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.module.service.\"deployment.wsba-participant-completion.war\".main is missing [jboss.module.spec.service.\"deployment.arquillian-service\".main]"], > "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => { > "Services that were unable to start:" => ["jboss.deployment.unit.\"wsba-participant-completion.war\".FIRST_MODULE_USE"], > "Services that may be the cause:" => [ > "jboss.module.spec.service.\"deployment.arquillian-service\".main", > "jboss.txn.TransactionSynchronizationRegistry", > "jboss.txn.UserTransactionRegistry" > ] > } > } > ... > {noformat} > {noformat} > org.jboss.as.test.xts.simple.wsat.client.WSATTestCase Time elapsed: 1846 sec <<< ERROR! > org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: wsat.war > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83) > ... > Caused by: java.lang.Exception: { > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.module.service.\"deployment.wsat.war\".main is missing [jboss.module.spec.service.\"deployment.arquillian-service\".main]"], > "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => { > "Services that were unable to start:" => ["jboss.deployment.unit.\"wsat.war\".FIRST_MODULE_USE"], > "Services that may be the cause:" => [ > "jboss.module.spec.service.\"deployment.arquillian-service\".main", > "jboss.txn.TransactionSynchronizationRegistry", > "jboss.txn.UserTransactionRegistry" > ] > } > } > ... > {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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1172) Support CommitOnePhase for REST-AT in TXFramework

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1172?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1172. --------------------------------- Assignee: Paul Robinson Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) Resolution: Won't Fix Applies to AT support in REST-AT which is being dropped in favour of JTA bridging. > Support CommitOnePhase for REST-AT in TXFramework > ------------------------------------------------- > > Key: JBTM-1172 > URL: https://issues.jboss.org/browse/JBTM-1172 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > Looks like this is missing from TxSupport too. -- 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, 4 months

1
0
0 / 0

[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: 6.0.0.Final (was: 5.0.0.Final) > 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 > Labels: assign > Fix For: 6.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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1107: -------------------------------- Summary: Recovery Support in Compensation API (was: Recovery Support in TXFramework) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Fix For: 5.0.0.Final > > -- 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, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2013