August 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1682) Create a simple non-transactional-resource compensations quickstart

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1682?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1682: -------------------------------- Original Estimate: 1 day (was: 3 days) Remaining Estimate: 1 day (was: 3 days) > Create a simple non-transactional-resource compensations quickstart > ------------------------------------------------------------------- > > Key: JBTM-1682 > URL: https://issues.jboss.org/browse/JBTM-1682 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M4 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > It should cover the first example covered in my JUDConn presentation and the associated blog post: http://jbossts.blogspot.co.uk/2013/05/compensating-transactions-when-acid... -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1682) Create a simple non-transactional-resource compensations quickstart

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1682?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1682: -------------------------------- Summary: Create a simple non-transactional-resource compensations quickstart (was: Create Quickstarts for using Compensations API) > Create a simple non-transactional-resource compensations quickstart > ------------------------------------------------------------------- > > Key: JBTM-1682 > URL: https://issues.jboss.org/browse/JBTM-1682 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M4 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Should cover the 3 examples covered in my JUDConn presentation and the associated blog post. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1785) TXBridge quickstart does not exist in master

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1785?focusedWorklogId=12429523&page=... ] Paul Robinson logged work on JBTM-1785: --------------------------------------- Author: Paul Robinson Created on: 02/Aug/13 12:15 PM Start Date: 02/Aug/13 12:15 PM Worklog Time Spent: 5 minutes Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 hour) Time Spent: 5 minutes Worklog Id: (was: 12429523) > TXBridge quickstart does not exist in master > -------------------------------------------- > > Key: JBTM-1785 > URL: https://issues.jboss.org/browse/JBTM-1785 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 5.0.0.M4 > > Original Estimate: 1 hour > Time Spent: 5 minutes > Remaining Estimate: 0 minutes > > Maybe I missed something but the /TXBridge tree from 4.17 is no longer present in master? This could be related to JBTM-1469 but there is no reference there that the quickstart has been deleted from master that I can see? -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1785) TXBridge quickstart does not exist in master

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1785?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1785. --------------------------------- Resolution: Rejected > TXBridge quickstart does not exist in master > -------------------------------------------- > > Key: JBTM-1785 > URL: https://issues.jboss.org/browse/JBTM-1785 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 5.0.0.M4 > > Original Estimate: 1 hour > Time Spent: 5 minutes > Remaining Estimate: 0 minutes > > Maybe I missed something but the /TXBridge tree from 4.17 is no longer present in master? This could be related to JBTM-1469 but there is no reference there that the quickstart has been deleted from master that I can see? -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1838) Document how to configure XTS to use SSL

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1838?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1838: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > Document how to configure XTS to use SSL > ---------------------------------------- > > Key: JBTM-1838 > URL: https://issues.jboss.org/browse/JBTM-1838 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, Documentation > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > Original Estimate: 1 day > Time Spent: 1 day > Remaining Estimate: 4 hours > > The documentation should show how to use 'https' for all communications. > I'm not sure what form the documentation should take. Given that the majority of configuration is actually related to enabling SSL for Web Services in general, I don't think it should all live in the XTS docs. Maybe we just add the XTS specific stuff there and link to the docs on how to enable SSL for WS. > We could also provide a JDF quickstart. However, the docs comprise of many bash commands, so this may not fit in well with a quickstart. > Other options are a community wiki page or blog posting. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1838) Document how to configure XTS to use SSL

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1838?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1838: ------------------------------------- Document currently lives here until I can figure out what to do with it: https://gist.github.com/paulrobinson/6019129 > Document how to configure XTS to use SSL > ---------------------------------------- > > Key: JBTM-1838 > URL: https://issues.jboss.org/browse/JBTM-1838 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, Documentation > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M4 > > Original Estimate: 1 day > Time Spent: 1 day > Remaining Estimate: 4 hours > > The documentation should show how to use 'https' for all communications. > I'm not sure what form the documentation should take. Given that the majority of configuration is actually related to enabling SSL for Web Services in general, I don't think it should all live in the XTS docs. Maybe we just add the XTS specific stuff there and link to the docs on how to enable SSL for WS. > We could also provide a JDF quickstart. However, the docs comprise of many bash commands, so this may not fit in well with a quickstart. > Other options are a community wiki page or blog posting. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1785) TXBridge quickstart does not exist in master

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1785?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1785: ------------------------------------- They were moved under XTS as they are really XTS related. https://github.com/jbosstm/quickstart/tree/master/XTS/jta-over-wsat https://github.com/jbosstm/quickstart/tree/master/XTS/legacy-api-quicksta... https://github.com/jbosstm/quickstart/tree/master/XTS/legacy-api-quicksta... This is consistent with the RTS bridging to JTA quickstarts. > TXBridge quickstart does not exist in master > -------------------------------------------- > > Key: JBTM-1785 > URL: https://issues.jboss.org/browse/JBTM-1785 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 5.0.0.M4 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Maybe I missed something but the /TXBridge tree from 4.17 is no longer present in master? This could be related to JBTM-1469 but there is no reference there that the quickstart has been deleted from master that I can see? -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1868) The application has to provide a javax.enterprise.inject.spi.Extension to use @CompensationScoped

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1868?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1868. --------------------------------- Resolution: Done > The application has to provide a javax.enterprise.inject.spi.Extension to use @CompensationScoped > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1868 > URL: https://issues.jboss.org/browse/JBTM-1868 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M4 > > -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1711) @CompensationScoped fails in CompensationHandler et al

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1711?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1711: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > @CompensationScoped fails in CompensationHandler et al > ------------------------------------------------------ > > Key: JBTM-1711 > URL: https://issues.jboss.org/browse/JBTM-1711 > 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.M4 > > Original Estimate: 2 days > Time Spent: 1 day > Remaining Estimate: 0 minutes > > Beans annotated with @CompensationScoped are injected correctly in the application. However, the scope fails to be created for CompensationHandler, ConfirmationHandler and TransactionLoggedHandler implementations. This is because they are invoked by XTS, not the application and thus Weld is not active on the thread. > The solution is to create the instance of the handlers using the BeanManager (this ensures Weld is active) and then set the ThreadContextClassLoader to the same as the one used by the application. This ensures that the application's Weld context is used when the handler is invoked. -- 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

10 years, 8 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: ----------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M4) > 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 > Priority: Minor > Fix For: 5.0.0.Final > > 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

10 years, 8 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 August 2013