April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1631) Quickstart PR testing broken for 4.17

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1631?focusedWorklogId=12429004&page=... ] Paul Robinson logged work on JBTM-1631: --------------------------------------- Author: Paul Robinson Created on: 12/Apr/13 11:06 AM Start Date: 12/Apr/13 11:06 AM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 2 hours) Time Spent: 2 hours Worklog Id: (was: 12429004) > Quickstart PR testing broken for 4.17 > ------------------------------------- > > Key: JBTM-1631 > URL: https://issues.jboss.org/browse/JBTM-1631 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator, Performance Testing > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 4.17.4 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Raised this PR with 1 cosmetic change: > https://github.com/jbosstm/quickstart/pull/72 > Failed: > http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-quickstar... > Despite 4.17 branch passing when tested with the following job: > http://172.17.131.2/view/Narayana+BlackTie/job/btny-EAP61-quickstarts-tac... > It's possible that it's a JDK version issue. btny-pulls-quickstarts uses JDK 7 as it tests master and 4.17. > btny-EAP61-quickstarts-taconic uses the default JDK, which is somehow set to "jdk1.6.0_31". -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1631) Quickstart PR testing broken for 4.17

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1631?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1631: ------------------------------------- It was actually caused by the ERROR_LEVEL not being detected properly. See: http://forums.techguy.org/software-development/803231-solved-errorlevel-b... > Quickstart PR testing broken for 4.17 > ------------------------------------- > > Key: JBTM-1631 > URL: https://issues.jboss.org/browse/JBTM-1631 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator, Performance Testing > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 4.17.4 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Raised this PR with 1 cosmetic change: > https://github.com/jbosstm/quickstart/pull/72 > Failed: > http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-quickstar... > Despite 4.17 branch passing when tested with the following job: > http://172.17.131.2/view/Narayana+BlackTie/job/btny-EAP61-quickstarts-tac... > It's possible that it's a JDK version issue. btny-pulls-quickstarts uses JDK 7 as it tests master and 4.17. > btny-EAP61-quickstarts-taconic uses the default JDK, which is somehow set to "jdk1.6.0_31". -- 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, 5 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1522?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1522: ------------------------------------- Are we able to release 4.17.4 without this fix, I guess so but wanted to check... > "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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1631) Quickstart PR testing broken for 4.17

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1631: ----------------------------------- Summary: Quickstart PR testing broken for 4.17 Key: JBTM-1631 URL: https://issues.jboss.org/browse/JBTM-1631 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Demonstrator, Performance Testing Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.17.4 Raised this PR with 1 cosmetic change: https://github.com/jbosstm/quickstart/pull/72 Failed: http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-quickstar... Despite 4.17 branch passing when tested with the following job: http://172.17.131.2/view/Narayana+BlackTie/job/btny-EAP61-quickstarts-tac... It's possible that it's a JDK version issue. btny-pulls-quickstarts uses JDK 7 as it tests master and 4.17. btny-EAP61-quickstarts-taconic uses the default JDK, which is somehow set to "jdk1.6.0_31". -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1598) version tags missed for all the sub-components

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1598: ------------------------------------- Great, I will apply the patches then - if there is anything else on JBTM-1526 you need please do give us a shout :) > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1497) Implement JTA 1.2 (when complete)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1497?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1497: -------------------------------- Fix Version/s: (was: 4.17.4) > Implement JTA 1.2 (when complete) > --------------------------------- > > Key: JBTM-1497 > URL: https://issues.jboss.org/browse/JBTM-1497 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 5.0.0.M3 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1598) version tags missed for all the sub-components

by Weinan Li (JIRA)

[ https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin.... ] Weinan Li commented on JBTM-1598: --------------------------------- Cool patches! Besides setting up the components versions, I see the dependency management sections are cleaned up and the version tags are used instead. Thank you very much for help Tom :-) > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1617) When testing pull requests do a rebase to the merge point

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1617?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1617: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1598) version tags missed for all the sub-components

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1598: ------------------------------------- Hi [~weinanli] would you be able to review the pull today do you think? I am hoping to put out a 4.17.4? Thanks, Tom > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1452) Distribution name of 4.17.x is narayana* rather than jbossts*

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1452?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1452: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Distribution name of 4.17.x is narayana* rather than jbossts* > ------------------------------------------------------------- > > Key: JBTM-1452 > URL: https://issues.jboss.org/browse/JBTM-1452 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.3 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > See https://www.jboss.org/jbosstm/downloads/4_17_3_Final -- 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, 5 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