February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1489) Create a blog post outlining integration with JBossWS

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1489?focusedWorklogId=12428738&page=... ] Paul Robinson logged work on JBTM-1489: --------------------------------------- Author: Paul Robinson Created on: 28/Feb/13 12:16 PM Start Date: 28/Feb/13 12:16 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 2 hours (was: 4 hours) Time Spent: 2 hours Worklog Id: (was: 12428738) > Create a blog post outlining integration with JBossWS > ----------------------------------------------------- > > Key: JBTM-1489 > URL: https://issues.jboss.org/browse/JBTM-1489 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M2 > > Original Estimate: 4 hours > Time Spent: 2 hours > Remaining Estimate: 2 hours > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1501) Create a Hudson job to build AS 7.2.0 branch

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1501?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1501: -------------------------------- Fix Version/s: 4.17.4 (was: 5.0.0.M3) > Create a Hudson job to build AS 7.2.0 branch > -------------------------------------------- > > Key: JBTM-1501 > URL: https://issues.jboss.org/browse/JBTM-1501 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System, Testing > Reporter: Paul Robinson > Fix For: 4.17.4 > > > Similar to the AS800 job. > We (incl hudson) need access to the private AS720 branch first. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1501) Create a Hudson job to build AS 7.2.0 branch

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1501?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1501: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Create a Hudson job to build AS 7.2.0 branch > -------------------------------------------- > > Key: JBTM-1501 > URL: https://issues.jboss.org/browse/JBTM-1501 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System, Testing > Reporter: Paul Robinson > Fix For: 4.17.4 > > > Similar to the AS800 job. > We (incl hudson) need access to the private AS720 branch first. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1501) Create a Hudson job to build AS 7.2.0 branch

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1501?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1501: ----------------------------------- Assignee: Tom Jenkinson > Create a Hudson job to build AS 7.2.0 branch > -------------------------------------------- > > Key: JBTM-1501 > URL: https://issues.jboss.org/browse/JBTM-1501 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System, Testing > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 4.17.4 > > > Similar to the AS800 job. > We (incl hudson) need access to the private AS720 branch first. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1490) Track JBossWS 4.2.0.Alpha1

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1490?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1490: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Track JBossWS 4.2.0.Alpha1 > -------------------------- > > Key: JBTM-1490 > URL: https://issues.jboss.org/browse/JBTM-1490 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Blocker > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Waiting for Alessio to release JBossWS 4.2.0.Alpha1 and have the component upgrade merged into AS master. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1501) Create a Hudson job to build AS 7.2.0 branch

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1501: ----------------------------------- Summary: Create a Hudson job to build AS 7.2.0 branch Key: JBTM-1501 URL: https://issues.jboss.org/browse/JBTM-1501 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System, Testing Reporter: Paul Robinson Fix For: 5.0.0.M3 Similar to the AS800 job. We (incl hudson) need access to the private AS720 branch first. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1211) Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1211?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1211: ----------------------------------- Fix Version/s: 5.0.0.M3 (was: 5.0.0.M2) > Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote > ------------------------------------------------------------------------------ > > Key: JBTM-1211 > URL: https://issues.jboss.org/browse/JBTM-1211 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS, Testing, Transaction Core > Affects Versions: 4.16.4 > Reporter: Paul Robinson > Assignee: Michael Musgrove > Fix For: 4.17.4, 5.0.0.M3 > > Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip > > Original Estimate: 1 week > Remaining Estimate: 1 week > > See: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java6/232 > {code} > Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote > [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 169.235 sec > {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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1209) XTS recovery tests failing due to a non-empty TXObjectStore after test complete

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1209?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1209: --------------------------------------- This looks like the same problem: http://172.17.131.2/job/narayana/170 > XTS recovery tests failing due to a non-empty TXObjectStore after test complete > ------------------------------------------------------------------------------- > > Key: JBTM-1209 > URL: https://issues.jboss.org/browse/JBTM-1209 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 5.0.0.M1 > Reporter: Paul Robinson > Assignee: Amos Feng > Fix For: 4.17.0, 5.0.0.M2 > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-java7/411/console > Looking at http://172.17.131.2/job/narayana-java7/411/artifact/XTS/localjunit/crash-... you will see: > {code} > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:92) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.junit.Assert.assertTrue(Assert.java:54) > at com.arjuna.qa.junit.BaseCrashTest.tearDown(BaseCrashTest.java:105) > {code} > This assertion checks that the TXObjectStore is empty after the test completes. For the three tests that failed in this job, the log was not empty. > Looking at the end of http://172.17.131.2/job/narayana-java7/411/artifact/XTS/localjunit/crash-... shows you: > {code} > [0m[0m10:36:04,605 INFO [stdout] (Periodic Recovery) rule.debug{trace remove committed state} : removed committed transaction 0:ffffac118303:4e49dd0f:50110ed5:10 > [0m[0m10:36:04,605 INFO [stdout] (Periodic Recovery) rule.debug{trace remove committed state} : !!!killing JVM!!! > {code} > This suggests that the transaction log was removed. However, I'm not sure that the Byteman script checks that the participant record has also been removed. It's possible that the AS is being killed slightly too early, before the participant record is removed. We should check other scripts to see if they wait for both logs to be removed. > [JBTM-1208] should help debug this problem if we get it again. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1500) Update Narayana to reference AS 8.0.0.Alpha1

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1500?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1500: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update Narayana to reference AS 8.0.0.Alpha1 > -------------------------------------------- > > Key: JBTM-1500 > URL: https://issues.jboss.org/browse/JBTM-1500 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1211) Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1211?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1211: ------------------------------------- Hi Mike, Please can you disable this test as we discussed in the meeting, before M2 would be perfect? Please can you ensure that your job that has the test enabled is not deleted until you have resolved the issue? Thanks, Tom > Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote > ------------------------------------------------------------------------------ > > Key: JBTM-1211 > URL: https://issues.jboss.org/browse/JBTM-1211 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS, Testing, Transaction Core > Affects Versions: 4.16.4 > Reporter: Paul Robinson > Assignee: Michael Musgrove > Fix For: 4.17.4, 5.0.0.M3 > > Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip > > Original Estimate: 1 week > Remaining Estimate: 1 week > > See: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java6/232 > {code} > Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote > [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 169.235 sec > {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

12 years, 8 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 February 2013