September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1929) Enhancement to TxProf to handle updated logging added in JBTM-1915

by Alex Creasy (JIRA)

[ https://issues.jboss.org/browse/JBTM-1929?page=com.atlassian.jira.plugin.... ] Alex Creasy updated JBTM-1929: ------------------------------ Description: A modification to the regex in TxFinalStatusHandler is required to handle the logging changes made to Narayana described in https://issues.jboss.org/browse/JBTM-1915. Also HandlerService::end method will need updating to recognise TwoPhaseOutcome strings instead of ActionStatus. (was: A modification to the regex in TxFinalStatusHandler is required to handle the logging changes made to Narayana described in https://issues.jboss.org/browse/JBTM-1915.) > Enhancement to TxProf to handle updated logging added in JBTM-1915 > ------------------------------------------------------------------ > > Key: JBTM-1929 > URL: https://issues.jboss.org/browse/JBTM-1929 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: TxProf > Reporter: Alex Creasy > Assignee: Paul Robinson > > A modification to the regex in TxFinalStatusHandler is required to handle the logging changes made to Narayana described in https://issues.jboss.org/browse/JBTM-1915. Also HandlerService::end method will need updating to recognise TwoPhaseOutcome strings instead of ActionStatus. -- 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, 2 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 Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1915?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1915: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done thanks for the contribution! > 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: 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, 2 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 Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1915?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1915: -------------------------------- Assignee: Alex Creasy (was: Tom Jenkinson) > 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: 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1870) Create a travel-agent quickstart using compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1870?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1870: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/93 > Create a travel-agent quickstart using compensations API > -------------------------------------------------------- > > Key: JBTM-1870 > URL: https://issues.jboss.org/browse/JBTM-1870 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > It should cover the second and third examples covered in my JUDConn presentation and the associated blog posts: > http://jbossts.blogspot.co.uk/2013/06/compensating-transactions-when-acid... > http://jbossts.blogspot.co.uk/2013/07/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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1850) org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT artefact is missing

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1850?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBTM-1850: ------------------------------------- I actually found the problem to be with my Maven version. It is recommended to use 3.0.3 but I had 3.0.5, so I figured I would try to upgrade first and if not downgrade. I tried 3.1.0 and that worked. Thanks > org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT artefact is missing > ----------------------------------------------------------------------------------- > > Key: JBTM-1850 > URL: https://issues.jboss.org/browse/JBTM-1850 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 4.17.6 > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP61/1809/console... > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] Building JBoss Application Server: JacORB Subsystem 7.2.0.Final > [INFO] ------------------------------------------------------------------------ > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > [WARNING] The POM for org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT is missing, no dependency information available > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > {code} > {code} > [ERROR] Failed to execute goal on project jboss-as-jacorb: Could not resolve dependencies for project org.jboss.as:jboss-as-jacorb:jar:7.2.0.Final: Could not find artifact org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExce... > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :jboss-as-jacorb > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1908) Running junit tests now verbose on command line

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1908?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1908: -------------------------------- Fix Version/s: 5.0.0.M5 > Running junit tests now verbose on command line > ----------------------------------------------- > > Key: JBTM-1908 > URL: https://issues.jboss.org/browse/JBTM-1908 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 5.0.0.M4 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M5 > > > Building all of TS today suddenly the output is ... > Running com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItemUnitTest > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.357 sec - in com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItemUnitTest > Running com.arjuna.ats.jts.TransactionServerUnitTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.318 sec - in com.arjuna.ats.jts.TransactionServerUnitTest > Running com.hp.mwtests.ts.jts.context.ContextManagerUnitTest > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.46 sec - in com.hp.mwtests.ts.jts.context.ContextManagerUnitTest > Running com.hp.mwtests.ts.jts.interposition.ArjunaInterpositionUnitTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.427 sec - in com.hp.mwtests.ts.jts.interposition.ArjunaInterpositionUnitTest > What is the point of the text after the time since it duplicates the text (class) on line above anyway? Can we turn this off please? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1908) Running junit tests now verbose on command line

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1908?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1908. --------------------------------- Resolution: Partially Completed I have reverted the version of surefire until SUREFIRE-1032 is resolved or a pressing need to upgrade becomes evident > Running junit tests now verbose on command line > ----------------------------------------------- > > Key: JBTM-1908 > URL: https://issues.jboss.org/browse/JBTM-1908 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 5.0.0.M4 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > > Building all of TS today suddenly the output is ... > Running com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItemUnitTest > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.357 sec - in com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItemUnitTest > Running com.arjuna.ats.jts.TransactionServerUnitTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.318 sec - in com.arjuna.ats.jts.TransactionServerUnitTest > Running com.hp.mwtests.ts.jts.context.ContextManagerUnitTest > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.46 sec - in com.hp.mwtests.ts.jts.context.ContextManagerUnitTest > Running com.hp.mwtests.ts.jts.interposition.ArjunaInterpositionUnitTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.427 sec - in com.hp.mwtests.ts.jts.interposition.ArjunaInterpositionUnitTest > What is the point of the text after the time since it duplicates the text (class) on line above anyway? Can we turn this off please? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1036) NP: Possible null pointer dereference (NP_NULL_ON_SOME_PATH)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1036?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1036: ----------------------------------- Assignee: Tom Jenkinson (was: Gytis Trikleris) > NP: Possible null pointer dereference (NP_NULL_ON_SOME_PATH) > ------------------------------------------------------------ > > Key: JBTM-1036 > URL: https://issues.jboss.org/browse/JBTM-1036 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, JTS, Transaction Core > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 1.ArjunaJTA/jdbc > Possible null pointer dereference of conn in com.arjuna.ats.internal.jdbc.recovery.BasicXARecovery.getXAResource() Line 169 > 2.ArjunaCore/arjuna > com.arjuna.ats.arjuna.StateManager Line 1234 > Possible null pointer dereference of action in com.arjuna.ats.arjuna.StateManager.forgetAction(BasicAction, boolean, int) > 3.ArjunaCore/arjuna > com.arjuna.ats.internal.arjuna.objectstore.HashedStore Line 131 > Possible null pointer dereference of aUid in com.arjuna.ats.internal.arjuna.objectstore.HashedStore.allObjUids(String, InputObjectState, int) > 4.ArjunaJTS/jtax > com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.coordinator.ServerTransaction Line 108 > Possible null pointer dereference of ServerTransaction._theXid in com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.coordinator.ServerTransaction.save_state(OutputObjectState, int) > 5.ArjunaJTS/jts > com.arjuna.ats.internal.jts.context.ContextManager Line 553 > Possible null pointer dereference of action in com.arjuna.ats.internal.jts.context.ContextManager.pushAction(ControlWrapper) > 6.ArjunaJTS/jts > com.arjuna.ats.jts.extensions.AtomicTransaction Line 617 > Possible null pointer dereference of AtomicTransaction._theAction in com.arjuna.ats.jts.extensions.AtomicTransaction.equals(Object) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1476) Document new XTS Features

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1476?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1476: -------------------------------- Assignee: Paul Robinson > Document new XTS Features > ------------------------- > > Key: JBTM-1476 > URL: https://issues.jboss.org/browse/JBTM-1476 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > > Plan for new XTS features and docs: > # Implement new feature > # Release a milestone of 5.0.0 > # Publish a blog post shortly after release > # Refine the feature based on community feedback > # Document the feature in the XTS xts_administration_and_development_guide before the 5.0.0.Final release (this issue is to do this item) > Here's a list of features that need documenting, so far: > JBTM-986 Automatically setup the client side handler chain > JBTM-1447 Create WebserviceFeature for TXBridge > New API for WS-AT (JTA) and WS-BA -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1041) IP: A parameter is dead upon entry to a method but overwritten (IP_PARAMETER_IS_DEAD_BUT_OVERWRITTEN)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1041?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1041: ----------------------------------- Assignee: Tom Jenkinson (was: Paul Robinson) > IP: A parameter is dead upon entry to a method but overwritten (IP_PARAMETER_IS_DEAD_BUT_OVERWRITTEN) > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-1041 > URL: https://issues.jboss.org/browse/JBTM-1041 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M5 > > > 1.XTS/WSCF > com.arjuna.mwlabs.wscf.model.sagas.arjunacore.ParticipantRecord Line 540 > The parameter toDelete to com.arjuna.mwlabs.wscf.model.sagas.arjunacore.ParticipantRecord.remove(AbstractRecord) is dead upon entry but overwritten > 2.XTS/WSCF > com.arjuna.mwlabs.wscf.model.twophase.arjunacore.ParticipantRecord Line 523 > The parameter toDelete to com.arjuna.mwlabs.wscf.model.twophase.arjunacore.ParticipantRecord.remove(AbstractRecord) is dead upon entry but overwritten -- 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, 2 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 September 2013