May 2013 - jbossts-issues - Jboss List Archives

[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 reassigned JBTM-1722: -------------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > 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: Gytis Trikleris > > 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

10 years, 11 months

1
0
0 / 0

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

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1722: -------------------------------------- Summary: 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 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1721) REST-AT participant support framework should support synchronizations

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1721: -------------------------------------- Summary: REST-AT participant support framework should support synchronizations Key: JBTM-1721 URL: https://issues.jboss.org/browse/JBTM-1721 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Components: REST Reporter: Michael Musgrove Assignee: Gytis Trikleris JBTM-1365 introduced an interface for simplifying participant registration into a REST-AT transaction by providing a callback for prepare/commit/rollback support. Please can we also have a similar mechanism for synchronizations. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1479?focusedWorklogId=12429311&page=... ] Gytis Trikleris logged work on JBTM-1479: ----------------------------------------- Author: Gytis Trikleris Created on: 29/May/13 6:13 AM Start Date: 29/May/13 6:13 AM Worklog Time Spent: 4 hours Issue Time Tracking ------------------- Time Spent: 1 week, 1 day, 7 hours, 20 minutes (was: 1 week, 1 day, 3 hours, 20 minutes) Worklog Id: (was: 12429311) > Create a quickstart to show how to use IronJacamar and JBTM inside tomcat > ------------------------------------------------------------------------- > > Key: JBTM-1479 > URL: https://issues.jboss.org/browse/JBTM-1479 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 1 week, 1 day, 7 hours, 20 minutes > Remaining Estimate: 0 minutes > > See JBTM-809 for the algorithm > You might want to put the startup in the context listener: > public class MyServletContextListener implements ServletContextListener { > public void contextInitialized(ServletContextEvent sce) { > // Initialize RecoveryManager > // Initialize TransactionManager > // Initialize IronJacamar > } > > @Override > public void contextDestroyed(ServletContextEvent sce) { > // Clean IronJacamar > // Clean TransactionManager > // Clean RecoveryManager > } > } > Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1712) perf problem in FileSystemStore.openAndLock

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1712?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-1712: ----------------------------------------------- James Livingston <jlivings(a)redhat.com> made a comment on [bug 968125|https://bugzilla.redhat.com/show_bug.cgi?id=968125] The transaction manager may perform expensive work which has no effect when the log file does not exist but the hierarchy does. The fix is at https://source.jboss.org/changelog/Narayana?cs=327461a3a8dae50e6621c0a560... and should be able to be easily backported > perf problem in FileSystemStore.openAndLock > ------------------------------------------- > > Key: JBTM-1712 > URL: https://issues.jboss.org/browse/JBTM-1712 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.16.4, 5.0.0.M2 > Reporter: Jonathan Halliday > Assignee: Mark Little > Fix For: 5.0.0.M3 > > > if(!file.exits()) > { > if(createHierarchy(file)) > incorrectly calls the expensive (because synchronized) createHierarchy method in the common case where the file does not exist (because it's a uniq named new tx record) but the directory hierarchy does (because it's the create-once hashed dir tree). This causes excessive contention on the FileSystemStore instance object monitor lock. Should probably be something more like > if(!file.getParent().exists()) > { > if(createHierarchy(file)) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1673) xatmi build with valgrind failure

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1673?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1673: ---------------------------- Description: http://172.17.131.2/job/blacktie-linux64-el5/1548/ http://172.17.131.2/job/blacktie-linux64-el5/1503/ http://172.17.131.2/job/blacktie-linux64-el5/1492/ was:http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1492/console > xatmi build with valgrind failure > --------------------------------- > > Key: JBTM-1673 > URL: https://issues.jboss.org/browse/JBTM-1673 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.Final > > > http://172.17.131.2/job/blacktie-linux64-el5/1548/ > http://172.17.131.2/job/blacktie-linux64-el5/1503/ > http://172.17.131.2/job/blacktie-linux64-el5/1492/ -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1720) Add a QA test run to test JTA recovery from a different node

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1720: -------------------------------------- Summary: Add a QA test run to test JTA recovery from a different node Key: JBTM-1720 URL: https://issues.jboss.org/browse/JBTM-1720 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Testing Affects Versions: 5.0.0.M2 Reporter: Michael Musgrove Assignee: Tom Jenkinson JBTM-1644 was raised to document how to recover a local JTA object store from a different node. Now that we have it in the documentation we need to test it in QA. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1016) Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1016: -------------------------------- Fix Version/s: 5.0.0.M4 (was: 5.0.0.M3) > Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code > ------------------------------------------------------------------------------------- > > Key: JBTM-1016 > URL: https://issues.jboss.org/browse/JBTM-1016 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Amos Feng > Fix For: 5.0.0.M4 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > I've found many bugs in the XTS crash recovery tests that where due to changes being made to the XTS code without updating the byteman scripts. The problem is that these inconsistencies often go unnoticed when the tests run, until you notice a failure in the test. > Can we run bmcheck as part of the maven build and make the build fail if it detects errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin > NOTE: Before raising the pull req it will be necessary to resolve any the discovered errors. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1691) Auto-merge in narayana.sh is not robust enough

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1691?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1691: -------------------------------- Fix Version/s: 5.0.0.M4 (was: 5.0.0.M3) > Auto-merge in narayana.sh is not robust enough > ---------------------------------------------- > > Key: JBTM-1691 > URL: https://issues.jboss.org/browse/JBTM-1691 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.M4 > > > This can't be auto=merged: > {code} > <<<<<<< HEAD > <version.org.jboss.jbossts.jbossjts>5.0.0.M2</version.org.jboss.jbossts.jbossjts> > <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M2</version.org.jboss.jbossts.jbossjts-integration> > <version.org.jboss.jbossts.jbossxts>5.0.0.M2</version.org.jboss.jbossts.jbossxts> > <version.org.jboss.jboss-vfs>3.2.0.Beta1</version.org.jboss.jboss-vfs> > <version.org.jboss.jbossts.narayana>5.0.0.M2</version.org.jboss.jbossts.narayana> > ======= > <version.org.jboss.jbossts.jbossjts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts> > <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts-integration> > <version.org.jboss.jbossts.jbossxts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossxts> > <version.org.jboss.jboss-vfs>3.1.0.Final</version.org.jboss.jboss-vfs> > <version.org.jboss.jbossts.narayana>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.narayana> > >>>>>>> Upgrade Narayana to 5.0.0.M3-SNAPSHOT > {code} > Our current strategy will take our version which results in the old version of jboss-vfs being used, which in turn causes a build failure in WildFly. > Maybe we should remove the auto-merge and replace with a manual intervention when a conflict occurs? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1709) NPE during deploy the restat-web.war

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1709?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1709: -------------------------------- Fix Version/s: 5.0.0.M4 (was: 5.0.0.M3) > NPE during deploy the restat-web.war > ------------------------------------ > > Key: JBTM-1709 > URL: https://issues.jboss.org/browse/JBTM-1709 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Server Integration, BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.M4 > > > http://172.17.131.2/job/blacktie-linux64-el5/1545/ > {noformat} > 13:38:34,246 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.undertow.deployment.default-host./rest-tx: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./rest-tx: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > 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] > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > at io.undertow.servlet.core.CompositeThreadSetupAction$1.tearDown(CompositeThreadSetupAction.java:59) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:196) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.NullPointerException > at org.jboss.jca.core.connectionmanager.ccm.CachedConnectionManagerImpl.popMetaAwareObject(CachedConnectionManagerImpl.java:240) > at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.teardown(CachedConnectionManagerSetupProcessor.java:107) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$1$1.tearDown(UndertowDeploymentInfoService.java:214) > at io.undertow.servlet.core.CompositeThreadSetupAction$1.tearDown(CompositeThreadSetupAction.java:52) > ... 7 more > {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

10 years, 11 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 May 2013