April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1522) "no XTS application recovery module found" during XTS Recovery Tests

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1522?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1522: ------------------------------------- Here's some examples of other ways to initialise the application. http://blog.eisele.net/2010/12/seven-ways-to-get-things-started-java.html It's not yet clear to me, if any will wait unill the server has finished booting. > "no XTS application recovery module found" during XTS Recovery Tests > -------------------------------------------------------------------- > > Key: JBTM-1522 > URL: https://issues.jboss.org/browse/JBTM-1522 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Attachments: 2013-04-01_jbtm-1522_outputs.zip, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit-output.txt, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output.txt, com.arjuna.qa.junit.TestBACrashDuringCommit.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit-output.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.txt > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/... > Notice the following log is displayed repeatedly until the test gives up waiting for recovery: > {code} > WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > {code} > This error comes from org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple#recoverParticipants(). In particular: > {code} > if (!found) { > // we failed to find a helper to convert a participant record so log a warning > // but leave it in the table for next time > RecoveryLogger.i18NLogger.warn_participant_at_XTSATRecoveryModule_4(participantRecoveryRecord.getId()); > } > {code} > It looks like the code is unable to restore the participant from the log due to restoreParticipant(XTSATRecoveryModule module) returning false. There is ParticipantRecoveryRecord in the log as you can see it dumped to the console in the above log. Maybe there is a problem with that log, or maybe we are missing another log entry? > This problem is intermittent, so it's unlikely that you will see this happen when you attach a debugger. However, we could attach a debugger to see what happens in the normal case and also to inspect the log to see if anything is missing in the failing case. But I have a cunning plan... > h4.Cunning Plan > We need to get a copy of the failing log, before recovery is attempted. We should then be able to use that log to reproduce the issue on our own machines. Steps to take: > # Update BaseCrashTest to copy the contents of the tx-object-store to a unique folder location (So we can retrieve it later for a failed run). Make sure you create the folder structure under target/surefire-reports so that CI archives it off. Do the copy between controller.kill and controller.start. This way we get the log before the recovery manager has had chance to tamper with it. > # Update the "narayana-JBTM-1522" job in CI to use your branch, containing the change above. > # Configure the job to run @hourly until it fails with this problem. > # Take a copy of the tx-object-store from the failing test and then put it in place on your AS8 build. > # Boot the AS and confirm that the issue is reproduced. > # You can now keep putting the tx-object-store back in place every time you need to reproduce the issue. > # Attach a debugger to find out what the problem is. -- 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-1598) version tags missed for all the sub-components

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin.... ] Work on JBTM-1598 started by Gytis Trikleris. > version tags missed for all the sub-components > ---------------------------------------------- > > Key: JBTM-1598 > URL: https://issues.jboss.org/browse/JBTM-1598 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Weinan Li > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Original Estimate: 1 hour > Time Spent: 1 day, 1 hour, 30 minutes > Remaining Estimate: 0 minutes > > Hi Tom, the problem I've found is that all the dependencies of its own components are lack of version section. For example: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > </dependency> > </dependencies> > {code} > Should be: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > <version>${project.version}</version> > </dependency> > </dependencies> > {code} > Could you please help to add these tags? Thanks! -- 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-1598) version tags missed for all the sub-components

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1598: ---------------------------------- Status: Open (was: Pull Request Sent) TXBridge tests fail on master > version tags missed for all the sub-components > ---------------------------------------------- > > Key: JBTM-1598 > URL: https://issues.jboss.org/browse/JBTM-1598 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Weinan Li > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Original Estimate: 1 hour > Time Spent: 1 day, 1 hour, 30 minutes > Remaining Estimate: 0 minutes > > Hi Tom, the problem I've found is that all the dependencies of its own components are lack of version section. For example: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > </dependency> > </dependencies> > {code} > Should be: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > <version>${project.version}</version> > </dependency> > </dependencies> > {code} > Could you please help to add these tags? Thanks! -- 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-1617) When testing pull requests do a rebase to the merge point

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1617?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1617: ---------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/264, https://github.com/jbosstm/narayana/pull/265, https://github.com/jbosstm/narayana/pull/270, https://github.com/jbosstm/narayana/pull/271 (was: https://github.com/jbosstm/narayana/pull/264, https://github.com/jbosstm/narayana/pull/265) > When testing pull requests do a rebase to the merge point > --------------------------------------------------------- > > Key: JBTM-1617 > URL: https://issues.jboss.org/browse/JBTM-1617 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Original Estimate: 2 hours > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 0 minutes > > These instructions can go in the pull job config rather than narayana.sh I think as they do a full clean and that would be dangerous on a dev box > # Clean up the local repo > git rebase --abort > rm -rf .git/rebase-apply > git clean -f -d -x > # Work out the branch point > git branch -D 4.17 > git branch 4.17 origin/4.17 > git branch -D master > git branch master origin/master > myRev=`git rev-parse HEAD` > ancestor417=`git merge-base $myRev 4.17` > ancestorMaster=`git merge-base $myRev master` > distanceFromMaster=`git log $ancestorMaster..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' '` > distanceFrom417=`git log $ancestor417..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' '` > if [ "$distanceFromMaster" -lt "$distanceFrom417" ] > then > export BRANCHPOINT=master > else > export BRANCHPOINT=4.17 > fi > # Update the pull to head > git pull --rebase --ff-only origin $BRANCHPOINT > # if this fails ($? -ne 0) fail the build and tell the committer (commentOnPull) that they need to rebase -- 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-1617) When testing pull requests do a rebase to the merge point

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1617?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1617: ---------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/264, https://github.com/jbosstm/narayana/pull/265 (was: https://github.com/jbosstm/narayana/pull/264, https://github.com/jbosstm/narayana/pull/265, https://github.com/jbosstm/narayana/pull/270, https://github.com/jbosstm/narayana/pull/271) > When testing pull requests do a rebase to the merge point > --------------------------------------------------------- > > Key: JBTM-1617 > URL: https://issues.jboss.org/browse/JBTM-1617 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Original Estimate: 2 hours > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 0 minutes > > These instructions can go in the pull job config rather than narayana.sh I think as they do a full clean and that would be dangerous on a dev box > # Clean up the local repo > git rebase --abort > rm -rf .git/rebase-apply > git clean -f -d -x > # Work out the branch point > git branch -D 4.17 > git branch 4.17 origin/4.17 > git branch -D master > git branch master origin/master > myRev=`git rev-parse HEAD` > ancestor417=`git merge-base $myRev 4.17` > ancestorMaster=`git merge-base $myRev master` > distanceFromMaster=`git log $ancestorMaster..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' '` > distanceFrom417=`git log $ancestor417..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' '` > if [ "$distanceFromMaster" -lt "$distanceFrom417" ] > then > export BRANCHPOINT=master > else > export BRANCHPOINT=4.17 > fi > # Update the pull to head > git pull --rebase --ff-only origin $BRANCHPOINT > # if this fails ($? -ne 0) fail the build and tell the committer (commentOnPull) that they need to rebase -- 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-1617) When testing pull requests do a rebase to the merge point

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1617?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1617: ---------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/264, https://github.com/jbosstm/narayana/pull/265, https://github.com/jbosstm/narayana/pull/270, https://github.com/jbosstm/narayana/pull/271 (was: https://github.com/jbosstm/narayana/pull/264, https://github.com/jbosstm/narayana/pull/265) > When testing pull requests do a rebase to the merge point > --------------------------------------------------------- > > Key: JBTM-1617 > URL: https://issues.jboss.org/browse/JBTM-1617 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > These instructions can go in the pull job config rather than narayana.sh I think as they do a full clean and that would be dangerous on a dev box > # Clean up the local repo > git rebase --abort > rm -rf .git/rebase-apply > git clean -f -d -x > # Work out the branch point > git branch -D 4.17 > git branch 4.17 origin/4.17 > git branch -D master > git branch master origin/master > myRev=`git rev-parse HEAD` > ancestor417=`git merge-base $myRev 4.17` > ancestorMaster=`git merge-base $myRev master` > distanceFromMaster=`git log $ancestorMaster..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' '` > distanceFrom417=`git log $ancestor417..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' '` > if [ "$distanceFromMaster" -lt "$distanceFrom417" ] > then > export BRANCHPOINT=master > else > export BRANCHPOINT=4.17 > fi > # Update the pull to head > git pull --rebase --ff-only origin $BRANCHPOINT > # if this fails ($? -ne 0) fail the build and tell the committer (commentOnPull) that they need to rebase -- 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-1617) When testing pull requests do a rebase to the merge point

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1617?focusedWorklogId=12429097&page=... ] Gytis Trikleris logged work on JBTM-1617: ----------------------------------------- Author: Gytis Trikleris Created on: 16/Apr/13 10:37 AM Start Date: 16/Apr/13 10:37 AM Worklog Time Spent: 30 minutes Issue Time Tracking ------------------- Time Spent: 2 hours, 30 minutes (was: 2 hours) Worklog Id: (was: 12429097) > When testing pull requests do a rebase to the merge point > --------------------------------------------------------- > > Key: JBTM-1617 > URL: https://issues.jboss.org/browse/JBTM-1617 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Original Estimate: 2 hours > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 0 minutes > > These instructions can go in the pull job config rather than narayana.sh I think as they do a full clean and that would be dangerous on a dev box > # Clean up the local repo > git rebase --abort > rm -rf .git/rebase-apply > git clean -f -d -x > # Work out the branch point > git branch -D 4.17 > git branch 4.17 origin/4.17 > git branch -D master > git branch master origin/master > myRev=`git rev-parse HEAD` > ancestor417=`git merge-base $myRev 4.17` > ancestorMaster=`git merge-base $myRev master` > distanceFromMaster=`git log $ancestorMaster..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' '` > distanceFrom417=`git log $ancestor417..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' '` > if [ "$distanceFromMaster" -lt "$distanceFrom417" ] > then > export BRANCHPOINT=master > else > export BRANCHPOINT=4.17 > fi > # Update the pull to head > git pull --rebase --ff-only origin $BRANCHPOINT > # if this fails ($? -ne 0) fail the build and tell the committer (commentOnPull) that they need to rebase -- 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-1597) xatmi job crashed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1597?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1597: ------------------------------------- There should be, if there isn't please can you request [~jhalliday] for it to be added onto the CI cluster > xatmi job crashed > ----------------- > > Key: JBTM-1597 > URL: https://issues.jboss.org/browse/JBTM-1597 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1462/console > It happens at the following > {code} > TestTPRecv::tearDown { > if(cd !=-1) { > ::tpdiscon(cd); > } > } > {code} > it looks like a memory issue in HybridSocketEndpointQueue::_send() and I think the test might crash with SIGSEV. -- 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-1632) blacktie-linux.sh contains hard-coded versions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1632?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1632: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > blacktie-linux.sh contains hard-coded versions > ---------------------------------------------- > > Key: JBTM-1632 > URL: https://issues.jboss.org/browse/JBTM-1632 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Demonstrator > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M3 > > > See: > https://github.com/jbosstm/quickstart/blob/master/blacktie/test/blacktie-... > In particular, 5.0.0.M2-SNAPSHOT, in: > {code} > ant -f $WORKSPACE/blacktie/test/initializeBlackTie.xml -Dbasedir=.. -DJBOSS_HOME=$JBOSS_HOME -DBT_HOME=$WORKSPACE/blacktie/target/dist/ -DVERSION=5.0.0.M2-SNAPSHOT -DMACHINE_ADDR=`hostname` -DJBOSSAS_IP_ADDR=$JBOSSAS_IP_ADDR -DBLACKTIE_DIST_HOME=$BLACKTIE_DIST_HOME initializeJBoss initializeBlackTie -debug > {code} > It would be better if we could infer this from the quickstart project version. -- 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-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?page=com.atlassian.jira.plugin.... ] Work on JBTM-1479 stopped by Gytis Trikleris. > 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.M3 > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 4 days, 6 hours, 30 minutes > Remaining Estimate: 2 days > > 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

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