July 2013 - jbossts-issues - Jboss List Archives

[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: Critical (was: Major) > 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: Critical > Fix For: 5.0.0.M4 > > Original Estimate: 1 week > Time Spent: 4 hours, 30 minutes > 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1364) Migrate "REST-AT to JTA" bridge into RTS component

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1364?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1364: -------------------------------- Priority: Critical (was: Major) > Migrate "REST-AT to JTA" bridge into RTS component > -------------------------------------------------- > > Key: JBTM-1364 > URL: https://issues.jboss.org/browse/JBTM-1364 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, REST, TxBridge > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Critical > Labels: assign > Fix For: 5.0.0.M4 > > Original Estimate: 1 week > Time Spent: 1 week, 2 days, 4 hours, 45 minutes > Remaining Estimate: 0 minutes > > The task is to the work Gytis did on his internship and migrate it into the REST-TX project. > Tasks: > 1. Review the current solution looking for: > 1.1 Major issues that prevent an initial release > 1.2 Test coverage > 2. Make any required changes > 3. Merge into the REST-TX project > 4. Migrate the quickstarts accross > 5. Create a blog post > 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1750) Create Quickstarts for REST-AT bridge

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1750?focusedWorklogId=12429514&page=... ] Gytis Trikleris logged work on JBTM-1750: ----------------------------------------- Author: Gytis Trikleris Created on: 30/Jul/13 8:27 AM Start Date: 30/Jul/13 8:20 AM Worklog Time Spent: 3 hours Work Description: JPA and JMS quickstarts work but they need refactoring. However, that can be done after the M4 is released. I have removed combined quickstart (JPA and JMS in one) because it does not give much more benefit. Also, it requires additional work with maven dependency resolver since apparently its API have changed. Issue Time Tracking ------------------- Remaining Estimate: 1 hour (was: 1 day) Time Spent: 6 hours (was: 3 hours) Worklog Id: (was: 12429514) > Create Quickstarts for REST-AT bridge > ------------------------------------- > > Key: JBTM-1750 > URL: https://issues.jboss.org/browse/JBTM-1750 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Demonstrator, REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > Original Estimate: 3 hours > Time Spent: 6 hours > Remaining Estimate: 1 hour > > We should take the ones from Gytis' dissertation and bring them up to the standard of the existing ones (Which they may already be). and then merge into our quickstart repo. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1750) Create Quickstarts for REST-AT bridge

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1750?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1750: --------------------------------------- JPA and JMS quickstarts work but they need refactoring. However, that can be done after the M4 is released. I have removed combined quickstart (JPA and JMS in one) because it does not give much more benefit. Also, it requires additional work with maven dependency resolver since apparently its API have changed. Currently quickstarts can be found here: https://github.com/Gytis/quickstart/tree/master-JBTM-1750/rts/at/bridge > Create Quickstarts for REST-AT bridge > ------------------------------------- > > Key: JBTM-1750 > URL: https://issues.jboss.org/browse/JBTM-1750 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Demonstrator, REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > Original Estimate: 3 hours > Time Spent: 6 hours > Remaining Estimate: 1 hour > > We should take the ones from Gytis' dissertation and bring them up to the standard of the existing ones (Which they may already be). and then merge into our quickstart repo. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1641) EAP 6.1 CNFE org.jboss.tm.TxManager (from Module org.jboss.jboss-transaction-spi:main)

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1641?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1641: ----------------------------------- Original Estimate: 2 days (was: 1 day) Remaining Estimate: 2 days (was: 1 day) > EAP 6.1 CNFE org.jboss.tm.TxManager (from Module org.jboss.jboss-transaction-spi:main) > -------------------------------------------------------------------------------------- > > Key: JBTM-1641 > URL: https://issues.jboss.org/browse/JBTM-1641 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Application Server Integration > Affects Versions: 4.17.3 > Reporter: Darryl Miles > Assignee: Michael Musgrove > Fix For: 5.0.0.M4 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > When enabling additional logging to system DEBUG on startup of standalone-full.xml it is possible to see: > 07:15:40,780 DEBUG [org.jboss.tm.TransactionManagerLocator] (MSC service thread 1-2) Unable to lookup: java:/TransactionManager: javax.naming.NameNotFoundException: Error looking up TransactionManager, service service jboss.naming.context.java.TransactionManager is not started > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:132) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:80) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:120) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:183) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_17] > at org.jboss.tm.TransactionManagerLocator.tryJNDI(TransactionManagerLocator.java:150) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.TransactionManagerLocator.locate(TransactionManagerLocator.java:131) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.TransactionManagerLocator.locateTransactionManager(TransactionManagerLocator.java:94) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<init>(ServerVMClientUserTransaction.java:93) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<clinit>(ServerVMClientUserTransaction.java:60) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:115) [jboss-as-transactions-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 07:15:40,786 DEBUG [org.jboss.tm.TransactionManagerLocator] (MSC service thread 1-2) Unable to instantiate legacy transaction manager: java.lang.ClassNotFoundException: org.jboss.tm.TxManager from [Module "org.jboss.jboss-transaction-spi:main" from local module loader @634f6b14 (finder: local module finder @72ff20fb (roots: F:\Devel\deps\jboss-eap-6.1\modules,F:\Devel\deps\jboss-eap-6.1\modules\system\layers\base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.2.0.CR1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.2.0.CR1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.2.0.CR1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.2.0.CR1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.2.0.CR1] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:188) [rt.jar:1.7.0_17] > at org.jboss.tm.TransactionManagerLocator.usePrivateAPI(TransactionManagerLocator.java:172) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.TransactionManagerLocator.locate(TransactionManagerLocator.java:133) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.TransactionManagerLocator.locateTransactionManager(TransactionManagerLocator.java:94) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<init>(ServerVMClientUserTransaction.java:93) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<clinit>(ServerVMClientUserTransaction.java:60) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:115) [jboss-as-transactions-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1722) REST-AT participant support framework should have associated quickstarts

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1722?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1722: ----------------------------------- Fix Version/s: 5.0.0.M4 > REST-AT participant support framework should have associated quickstarts > ------------------------------------------------------------------------ > > Key: JBTM-1722 > URL: https://issues.jboss.org/browse/JBTM-1722 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.M4 > > > JBTM-1365 introduced the RTS wildfly subsystem and an interface for simplifying participant registration into a REST-AT transaction by providing callbacks for prepare/commit/rollback. We need some quickstarts that show how to use it: > - a standalone example similar to https://github.com/jbosstm/quickstart/tree/master/rest-tx/service showing the difference between the two approaches to building services > - showing integration with wildfly > - one for recovery > If we want to split the work between engineers that would be fine. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1722) REST-AT participant support framework should have associated quickstarts

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1722?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1722: ----------------------------------- Priority: Minor (was: Major) > REST-AT participant support framework should have associated quickstarts > ------------------------------------------------------------------------ > > Key: JBTM-1722 > URL: https://issues.jboss.org/browse/JBTM-1722 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M4 > > > JBTM-1365 introduced the RTS wildfly subsystem and an interface for simplifying participant registration into a REST-AT transaction by providing callbacks for prepare/commit/rollback. We need some quickstarts that show how to use it: > - a standalone example similar to https://github.com/jbosstm/quickstart/tree/master/rest-tx/service showing the difference between the two approaches to building services > - showing integration with wildfly > - one for recovery > If we want to split the work between engineers that would be fine. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1722) REST-AT participant support framework should have associated quickstarts

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1722?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1722: ----------------------------------- Original Estimate: 6 hours Remaining Estimate: 6 hours > REST-AT participant support framework should have associated quickstarts > ------------------------------------------------------------------------ > > Key: JBTM-1722 > URL: https://issues.jboss.org/browse/JBTM-1722 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M4 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > JBTM-1365 introduced the RTS wildfly subsystem and an interface for simplifying participant registration into a REST-AT transaction by providing callbacks for prepare/commit/rollback. We need some quickstarts that show how to use it: > - a standalone example similar to https://github.com/jbosstm/quickstart/tree/master/rest-tx/service showing the difference between the two approaches to building services > - showing integration with wildfly > - one for recovery > If we want to split the work between engineers that would be fine. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1556) provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1556?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1556: ----------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling > ---------------------------------------------------------------------------------------------- > > Key: JBTM-1556 > URL: https://issues.jboss.org/browse/JBTM-1556 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.3 > Reporter: Scott Marlow > Assignee: Michael Musgrove > Fix For: 5.0.0.M5 > > > When the Synchronization.afterCompletion is invoked for EE JPA containers, knowledge of whether the current thread is the Reaper thread (cancelling the transaction from a background thread). > The fix to this jira will help with handling the [JPA 2.1 container concurrency requirements|http://java.net/projects/jpa-spec/lists/jsr338-experts/archi...]. > Please implement the solution makes the most sense to you, as this will introduce an additional dependency between other systems and JBossTM/JBossTS that depend on the solution, that will likely be around for a long time. -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1853) RESTAT does not expose recovery URIs after a crash

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1853?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1853: ----------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > RESTAT does not expose recovery URIs after a crash > -------------------------------------------------- > > Key: JBTM-1853 > URL: https://issues.jboss.org/browse/JBTM-1853 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > The RESTAT coordinator creates a participant-recovery URI during participant enlistment. This URI should exist for as long as the participant participates in the transaction including during recovery time. After a coordinator crash GET requests return 404 instead of returning the participant resource URI -- 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2013