July 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1855?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1855: -------------------------------- Reporter: Crispin Boylan (was: Tom Jenkinson) > No unit tests for queue with RTS transport > ------------------------------------------ > > Key: JBTM-1855 > URL: https://issues.jboss.org/browse/JBTM-1855 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie, REST, Testing > Reporter: Crispin Boylan > Assignee: Amos Feng > Fix For: 5.0.0.M4 > > > There are currently no tests that use RTS for C++ queue tests. You can tell this as TXN_CFG is not specific in the btconfig.xml. > When TXN_CFG is manually added to the btconfig.xml the tests actually fail. -- 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-1855) No unit tests for queue with RTS transport

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1855: ----------------------------------- Summary: No unit tests for queue with RTS transport Key: JBTM-1855 URL: https://issues.jboss.org/browse/JBTM-1855 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: BlackTie, REST, Testing Reporter: Tom Jenkinson Assignee: Amos Feng Fix For: 5.0.0.M4 There are currently no tests that use RTS for C++ queue tests. You can tell this as TXN_CFG is not specific in the btconfig.xml. When TXN_CFG is manually added to the btconfig.xml the tests actually fail. -- 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-1854) Hornetq failures in CI test suite

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1854: -------------------------------------- Summary: Hornetq failures in CI test suite Key: JBTM-1854 URL: https://issues.jboss.org/browse/JBTM-1854 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 5.0.0.M3 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.0.M4 There were quite a few failures so I am simply listing them here and referencing the job for further investigation: CurrentTests01_Test036 jtsremote JTSRemote_ImplicitPropagationTest crashrecovery02_2 CrashRecovery02_2 - all of them crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) -- 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-1847) Update blacktie build to test with standalone-blacktie.xml

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1847?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1847: ---------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/378, https://github.com/jbosstm/quickstart/pull/82 (was: https://github.com/jbosstm/narayana/pull/378) > Update blacktie build to test with standalone-blacktie.xml > ---------------------------------------------------------- > > Key: JBTM-1847 > URL: https://issues.jboss.org/browse/JBTM-1847 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BlackTie, Build System, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.M4 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > when JBTM-1568 resolved, it can start jboss-as with the configuration standalone-blacktie.xml which has blacktie subsystem. It should not deploy the blacktie-stompconnect as it has been moved into wildfly codebase. > also it needs to change initializeJBoss.xml to copy this configuration and replace with it. -- 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-1847) Update blacktie build to test with standalone-blacktie.xml

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1847?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1847: --------------------------------- It also needs to change quickstart/blacktie/test/initializeJBoss.xml and blacktie-linux.sh and blacktie-vc9x32.bat > Update blacktie build to test with standalone-blacktie.xml > ---------------------------------------------------------- > > Key: JBTM-1847 > URL: https://issues.jboss.org/browse/JBTM-1847 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BlackTie, Build System, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.M4 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > when JBTM-1568 resolved, it can start jboss-as with the configuration standalone-blacktie.xml which has blacktie subsystem. It should not deploy the blacktie-stompconnect as it has been moved into wildfly codebase. > also it needs to change initializeJBoss.xml to copy this configuration and replace with it. -- 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-1847) Update blacktie build to test with standalone-blacktie.xml

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1847?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1847: ---------------------------- Component/s: Demonstrator > Update blacktie build to test with standalone-blacktie.xml > ---------------------------------------------------------- > > Key: JBTM-1847 > URL: https://issues.jboss.org/browse/JBTM-1847 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BlackTie, Build System, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.M4 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > when JBTM-1568 resolved, it can start jboss-as with the configuration standalone-blacktie.xml which has blacktie subsystem. It should not deploy the blacktie-stompconnect as it has been moved into wildfly codebase. > also it needs to change initializeJBoss.xml to copy this configuration and replace with it. -- 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-1364) Migrate "REST-AT to JTA" bridge into RTS component

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1364?focusedWorklogId=12429502&page=... ] Gytis Trikleris logged work on JBTM-1364: ----------------------------------------- Author: Gytis Trikleris Created on: 21/Jul/13 7:16 PM Start Date: 21/Jul/13 7:15 PM Worklog Time Spent: 3 hours Issue Time Tracking ------------------- Remaining Estimate: 15 minutes (was: 1 day, 4 hours, 15 minutes) Time Spent: 1 week, 1 day, 6 hours, 45 minutes (was: 1 week, 1 day, 3 hours, 45 minutes) Worklog Id: (was: 12429502) > Migrate "REST-AT to JTA" bridge into RTS component > -------------------------------------------------- > > Key: JBTM-1364 > URL: https://issues.jboss.org/browse/JBTM-1364 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, REST, TxBridge > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M4 > > Original Estimate: 1 week > Time Spent: 1 week, 1 day, 6 hours, 45 minutes > Remaining Estimate: 15 minutes > > The task is to the work Gytis did on his internship and migrate it into the REST-TX project. > Tasks: > 1. Review the current solution looking for: > 1.1 Major issues that prevent an initial release > 1.2 Test coverage > 2. Make any required changes > 3. Merge into the REST-TX project > 4. Migrate the quickstarts accross > 5. Create a blog post > 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy. -- 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-1853) RESTAT does not expose recovery URIs after a crash

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1853: -------------------------------------- Summary: RESTAT does not expose recovery URIs after a crash Key: JBTM-1853 URL: https://issues.jboss.org/browse/JBTM-1853 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Affects Versions: 5.0.0.M3 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.0.M4 The RESTAT coordinator creates a participant-recovery URI during participant enlistment. This URI should exist for as long as the participant participates in the transaction including during recovery time. After a coordinator crash GET requests return 404 instead of returning the participant resource URI -- 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-1852) Rollback local participant and remove log entry if transaction is not active during recovery.

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1852?focusedWorklogId=12429500&page=... ] Gytis Trikleris logged work on JBTM-1852: ----------------------------------------- Author: Gytis Trikleris Created on: 19/Jul/13 12:33 PM Start Date: 19/Jul/13 12:33 PM Worklog Time Spent: 2 hours, 15 minutes Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 2 hours) Time Spent: 2 hours, 45 minutes (was: 30 minutes) Worklog Id: (was: 12429500) > Rollback local participant and remove log entry if transaction is not active during recovery. > --------------------------------------------------------------------------------------------- > > Key: JBTM-1852 > URL: https://issues.jboss.org/browse/JBTM-1852 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > Original Estimate: 30 minutes > Time Spent: 2 hours, 45 minutes > Remaining Estimate: 0 minutes > > Recovery is not working properly in REST-AT multiplexor. Problem happens if both coordinator and participant crashes straight after the participant is prepared but before the coordinator gets the vote. After both parties are recovered, coordinator does not know about the transaction. Therefore, participant has to be rolled back. However, multiplexor keeps participant active. -- 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-1364) Migrate "REST-AT to JTA" bridge into RTS component

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1364?focusedWorklogId=12429501&page=... ] Gytis Trikleris logged work on JBTM-1364: ----------------------------------------- Author: Gytis Trikleris Created on: 19/Jul/13 12:34 PM Start Date: 19/Jul/13 12:33 PM Worklog Time Spent: 5 hours, 15 minutes Issue Time Tracking ------------------- Remaining Estimate: 1 day, 4 hours, 15 minutes (was: 2 days, 1 hour, 30 minutes) Time Spent: 1 week, 1 day, 3 hours, 45 minutes (was: 1 week, 6 hours, 30 minutes) Worklog Id: (was: 12429501) > Migrate "REST-AT to JTA" bridge into RTS component > -------------------------------------------------- > > Key: JBTM-1364 > URL: https://issues.jboss.org/browse/JBTM-1364 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, REST, TxBridge > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M4 > > Original Estimate: 1 week > Time Spent: 1 week, 1 day, 3 hours, 45 minutes > Remaining Estimate: 1 day, 4 hours, 15 minutes > > The task is to the work Gytis did on his internship and migrate it into the REST-TX project. > Tasks: > 1. Review the current solution looking for: > 1.1 Major issues that prevent an initial release > 1.2 Test coverage > 2. Make any required changes > 3. Merge into the REST-TX project > 4. Migrate the quickstarts accross > 5. Create a blog post > 5.1 Consider what the end user will need to do to use this technology. We may want to wait until REST-AT and this Bridge are shipped with a Narayana build of AS7. Otherwise the steps to get this working could be rather lengthy. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2013