September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1940) Server-side XTS handlers not added if @WebService#portName is missing

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1940?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1940: -------------------------------- Summary: Server-side XTS handlers not added if @WebService#portName is missing (was: Deployment fails if @WebService#portName is missing) > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: JBTM-1940 > URL: https://issues.jboss.org/browse/JBTM-1940 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > Try removing portName attribute from one of the test services in the TXFramework suite. You will see that deployment fails. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1946) Remove quickstarts that use the old Compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1946?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1946: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove quickstarts that use the old Compensations API > ----------------------------------------------------- > > Key: JBTM-1946 > URL: https://issues.jboss.org/browse/JBTM-1946 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > wsba-to-jta and wsba-simple where replaced with travel-agent and non-transactional_resource (respectively). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1942) Additional trace logging to enable TxProf to obtain record id of XAResourceRecords.

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1942?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1942. --------------------------------- Resolution: Done > Additional trace logging to enable TxProf to obtain record id of XAResourceRecords. > ----------------------------------------------------------------------------------- > > Key: JBTM-1942 > URL: https://issues.jboss.org/browse/JBTM-1942 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Alex Creasy > Assignee: Alex Creasy > Fix For: 5.0.0.M5, 4.17.11 > > > Additional logging added in JBTM-1915 can only be utilised by TxProf for JTS transactions. This is because TxProf identifies resources in JTS transactions by their record uid, whereas in JTA transactions they are identified by the resource manager's JNDI name. Affixing the record UID to trace logging statements in XAResourceRecord will enable TxProf to provide the enhanced data for both JTA and JTS transactions -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1915) Enhancement to logging to output the status of prepare, commit and abort for each resource after they complete and the result of the transaction

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1915?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1915: -------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/435, https://github.com/jbosstm/narayana/pull/469 (was: https://github.com/jbosstm/narayana/pull/435) > Enhancement to logging to output the status of prepare, commit and abort for each resource after they complete and the result of the transaction > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1915 > URL: https://issues.jboss.org/browse/JBTM-1915 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Alex Creasy > Assignee: Alex Creasy > Fix For: 4.17.11, 5.0.0.M5 > > > Presently the transaction manager only outputs logging when beginning to prepare, commit or abort. Additional logging that shows the result of each resource asked to prepare / commit / abort and the result of the transaction is necessary for the txprof tool to diagnose common transactional problems. The proposal is to add an additional line of trace logging to the End, doPrepare, doCommit and doAbort methods in BasicAction.java. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1915) Enhancement to logging to output the status of prepare, commit and abort for each resource after they complete and the result of the transaction

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1915?page=com.atlassian.jira.plugin.... ] Paul Robinson reopened JBTM-1915: --------------------------------- Needs this fix merging: https://github.com/jbosstm/narayana/pull/469 > Enhancement to logging to output the status of prepare, commit and abort for each resource after they complete and the result of the transaction > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1915 > URL: https://issues.jboss.org/browse/JBTM-1915 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Alex Creasy > Assignee: Alex Creasy > Fix For: 4.17.11, 5.0.0.M5 > > > Presently the transaction manager only outputs logging when beginning to prepare, commit or abort. Additional logging that shows the result of each resource asked to prepare / commit / abort and the result of the transaction is necessary for the txprof tool to diagnose common transactional problems. The proposal is to add an additional line of trace logging to the End, doPrepare, doCommit and doAbort methods in BasicAction.java. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1942) Additional trace logging to enable TxProf to obtain record id of XAResourceRecords.

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1942?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1942: ------------------------------------- I was mistaken, the above commit is needed for JBTM-1915. Resolving this issue. > Additional trace logging to enable TxProf to obtain record id of XAResourceRecords. > ----------------------------------------------------------------------------------- > > Key: JBTM-1942 > URL: https://issues.jboss.org/browse/JBTM-1942 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Alex Creasy > Assignee: Alex Creasy > Fix For: 4.17.11, 5.0.0.M5 > > > Additional logging added in JBTM-1915 can only be utilised by TxProf for JTS transactions. This is because TxProf identifies resources in JTS transactions by their record uid, whereas in JTA transactions they are identified by the resource manager's JNDI name. Affixing the record UID to trace logging statements in XAResourceRecord will enable TxProf to provide the enhanced data for both JTA and JTS transactions -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1917) XTS*RecoveryManager.getRecoveryManager() can return null if application deployed before XTS starts

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1917?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1917: ------------------------------------- The polling is now merged into master. Gytis can you: 1. Remove the polling from tests. 2. Remove the polling from quickstarts 3. Create a 6.0.0.Final issue for doing this properly (via injection). > XTS*RecoveryManager.getRecoveryManager() can return null if application deployed before XTS starts > -------------------------------------------------------------------------------------------------- > > Key: JBTM-1917 > URL: https://issues.jboss.org/browse/JBTM-1917 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M5 > > > The problem is that there is currently no way of specifying that an application depends on XTS. Therefore it's possible that when the server starts, that the application can be deployed before XTS is started, thus a call to XTSBARecoveryManager.getRecoveryManager() or XTSATRecoveryManager.getRecoveryManager() will return null. > The workaround is to poll for the RecoveryManager until it is not null. > The fix is to have the RecoveryManager injected into the application via a Deployment Unit Processor that has a dependency on the XTS service. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1925) Enable remote debugger in JBossAS/WildFly for all tests

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1925?page=com.atlassian.jira.plugin.... ] Paul Robinson reassigned JBTM-1925: ----------------------------------- Assignee: Gytis Trikleris (was: Paul Robinson) Gytis, I've had a look at this issue and updated the description with what should now work. Tom and I have tried it out. It's going to be quite time-consuming, and I still have a few M5 issues left to do. Can you take a look at this please. Re-assign it back if you don't think you will have time to do it. > Enable remote debugger in JBossAS/WildFly for all tests > ------------------------------------------------------- > > Key: JBTM-1925 > URL: https://issues.jboss.org/browse/JBTM-1925 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 4.17.11, 5.0.0.M5 > > > We need to enable the debugger in all arquillian.xml files. To do this: > 1. Add this to each arquillian.xml: > {code} > <configuration> > <property name="javaVmArguments">${server.jvm.args}</property> > .... > </configuration> > {code} > 2. Update the server.jvm.args in each maven profile for running the Arquillian tests: > {code} > <server.jvm.args>..... ${jvm.args.debug}</server.jvm.args> > {code} > Look at the XTS/localjunit/pom.xml for an example. You will notice that not all Arquillian profiles configure the server.jvm.args. In which case you will need to add the config to match the others. > 3. Add this property to the root pom,xml: > {code} > <jvm.args.debug>-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n</jvm.args.debug> > {code} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1925) Enable remote debugger in JBossAS/WildFly for all tests

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1925?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1925: -------------------------------- Description: We need to enable the debugger in all arquillian.xml files. To do this: 1. Add this to each arquillian.xml: {code} <configuration> <property name="javaVmArguments">${server.jvm.args}</property> .... </configuration> {code} 2. Update the server.jvm.args in each maven profile for running the Arquillian tests: {code} <server.jvm.args>..... ${jvm.args.debug}</server.jvm.args> {code} Look at the XTS/localjunit/pom.xml for an example. You will notice that not all Arquillian profiles configure the server.jvm.args. In which case you will need to add the config to match the others. 3. Add this property to the root pom,xml: {code} <jvm.args.debug>-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n</jvm.args.debug> {code} was: This allows us to attach to hung AS instances and see what they are doing. Adding this to narayana.sh should do the trick: {code} echo JAVA_OPTS='"$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"' >> ./bin/standalone.conf {code} > Enable remote debugger in JBossAS/WildFly for all tests > ------------------------------------------------------- > > Key: JBTM-1925 > URL: https://issues.jboss.org/browse/JBTM-1925 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 4.17.11, 5.0.0.M5 > > > We need to enable the debugger in all arquillian.xml files. To do this: > 1. Add this to each arquillian.xml: > {code} > <configuration> > <property name="javaVmArguments">${server.jvm.args}</property> > .... > </configuration> > {code} > 2. Update the server.jvm.args in each maven profile for running the Arquillian tests: > {code} > <server.jvm.args>..... ${jvm.args.debug}</server.jvm.args> > {code} > Look at the XTS/localjunit/pom.xml for an example. You will notice that not all Arquillian profiles configure the server.jvm.args. In which case you will need to add the config to match the others. > 3. Add this property to the root pom,xml: > {code} > <jvm.args.debug>-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n</jvm.args.debug> > {code} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1946) Remove quickstarts that use the old Compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1946?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1946: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/96 > Remove quickstarts that use the old Compensations API > ----------------------------------------------------- > > Key: JBTM-1946 > URL: https://issues.jboss.org/browse/JBTM-1946 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > wsba-to-jta and wsba-simple where replaced with travel-agent and non-transactional_resource (respectively). -- 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, 3 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 September 2013