March 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1009) Ensure that the Object Store header for action records is the first item to be packed

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1009?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1009: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/233 > Ensure that the Object Store header for action records is the first item to be packed > ------------------------------------------------------------------------------------- > > Key: JBTM-1009 > URL: https://issues.jboss.org/browse/JBTM-1009 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.16.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.Final > > > Clone of https://issues.jboss.org/browse/JBTM-1008 but targeted at trunk: > Some action classes call super.save_state after save their own state which results in the record header being packed at arbitrary locations within the record. Ideally the tooling (ObjStoreBrowser) would like to read the header without having to know the specific class responsible for the record. > The equivalent fix for 4.16.0.Final was a quick fix to force offending classes to save/restore the parent classes state before the specific state. A more versatile solution is desirable for trunk, for example change the extension point (for saving state) from say save_state to save_state_impl and provide a final implementation of save_state in StateManager that calls out the classes implementation of save_state_impl after packing the header. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1521) QA_STRESS bash fu not correct

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1521?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1521: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/232 > QA_STRESS bash fu not correct > ----------------------------- > > Key: JBTM-1521 > URL: https://issues.jboss.org/browse/JBTM-1521 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.0.M3 > > > From ./scripts/hudson/narayana.sh: > for i in {1..200}; do echo run $i; ant -f run-tests.xml -Dtest.name=$QA_TESTGROUP onetest; [ $? = 0 ] || break; done > ok=$? > This doesn't do as expected, as OK is going to be 0 after the checking of whether it is zero! An example should help: > [tom@localhost narayana](master *) $ ls lded > ls: cannot access lded: No such file or directory > [tom@localhost narayana](master *) $ if [ $? -ne 0 ]; then echo $?; fi > 0 > You either need to cache OK in that loop, or change the logic a bit - hope it helps -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1521) QA_STRESS bash fu not correct

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1521: ----------------------------------- Summary: QA_STRESS bash fu not correct Key: JBTM-1521 URL: https://issues.jboss.org/browse/JBTM-1521 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Reporter: Tom Jenkinson Assignee: Michael Musgrove Fix For: 5.0.0.M3 >From ./scripts/hudson/narayana.sh: for i in {1..200}; do echo run $i; ant -f run-tests.xml -Dtest.name=$QA_TESTGROUP onetest; [ $? = 0 ] || break; done ok=$? This doesn't do as expected, as OK is going to be 0 after the checking of whether it is zero! An example should help: [tom@localhost narayana](master *) $ ls lded ls: cannot access lded: No such file or directory [tom@localhost narayana](master *) $ if [ $? -ne 0 ]; then echo $?; fi 0 You either need to cache OK in that loop, or change the logic a bit - hope it helps -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1516) XTS: Common configuration is not available

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1516?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1516: ------------------------------------- I noticed this is merged but there have been no further builds after merging, launching a build now. > XTS: Common configuration is not available > ------------------------------------------ > > Key: JBTM-1516 > URL: https://issues.jboss.org/browse/JBTM-1516 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Server Integration, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Time Spent: 40 minutes > Remaining Estimate: 0 minutes > > See: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/180/artifact/txfr... > Only happened for one test. Looks like an intermittent failure. If there was anything wrong with the config, it would fail for all tests. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1508) DisabledContextPropagationTest fails when standalone.xml content is updated by jboss-as

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1508?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1508: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/narayana/pull/231 > DisabledContextPropagationTest fails when standalone.xml content is updated by jboss-as > --------------------------------------------------------------------------------------- > > Key: JBTM-1508 > URL: https://issues.jboss.org/browse/JBTM-1508 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Currently we copy across a modified version of standalone-xts.xml. The problem is that this file needs to be kept in sync with the original. > The main problem is that these tests will fail every time an upstream change is made to standalone-xts.xml. > This problem is related with com.arjuna.wstx.tests.arq.ba.DisabledContextPropagationTest, com.arjuna.wstx.tests.arq.basic.DisabledContextPropagationTest, and org.jboss.jbossts.txbridge.tests.outbound.junit.DisabledContextPropagationTests -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1508) DisabledContextPropagationTest fails when standalone.xml content is updated by jboss-as

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1508?focusedWorklogId=12428746&page=... ] Gytis Trikleris logged work on JBTM-1508: ----------------------------------------- Author: Gytis Trikleris Created on: 07/Mar/13 6:58 AM Start Date: 07/Mar/13 6:58 AM Worklog Time Spent: 1 hour, 20 minutes Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 hour) Time Spent: 1 hour, 20 minutes Worklog Id: (was: 12428746) > DisabledContextPropagationTest fails when standalone.xml content is updated by jboss-as > --------------------------------------------------------------------------------------- > > Key: JBTM-1508 > URL: https://issues.jboss.org/browse/JBTM-1508 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Time Spent: 1 hour, 20 minutes > Remaining Estimate: 0 minutes > > Currently we copy across a modified version of standalone-xts.xml. The problem is that this file needs to be kept in sync with the original. > The main problem is that these tests will fail every time an upstream change is made to standalone-xts.xml. > This problem is related with com.arjuna.wstx.tests.arq.ba.DisabledContextPropagationTest, com.arjuna.wstx.tests.arq.basic.DisabledContextPropagationTest, and org.jboss.jbossts.txbridge.tests.outbound.junit.DisabledContextPropagationTests -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1508) DisabledContextPropagationTest fails when standalone.xml content is updated by jboss-as

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1508?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1508: ---------------------------------- Original Estimate: 1 hour (was: 4 hours) Remaining Estimate: 1 hour (was: 4 hours) > DisabledContextPropagationTest fails when standalone.xml content is updated by jboss-as > --------------------------------------------------------------------------------------- > > Key: JBTM-1508 > URL: https://issues.jboss.org/browse/JBTM-1508 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Currently we copy across a modified version of standalone-xts.xml. The problem is that this file needs to be kept in sync with the original. > The main problem is that these tests will fail every time an upstream change is made to standalone-xts.xml. > This problem is related with com.arjuna.wstx.tests.arq.ba.DisabledContextPropagationTest, com.arjuna.wstx.tests.arq.basic.DisabledContextPropagationTest, and org.jboss.jbossts.txbridge.tests.outbound.junit.DisabledContextPropagationTests -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1520) XMLFilePlugin fails to read the configuration if its path contains unicode characters

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/JBTM-1520?page=com.atlassian.jira.plugin.... ] Ivo Studensky resolved JBTM-1520. --------------------------------- Resolution: Done Committed in r38299. > XMLFilePlugin fails to read the configuration if its path contains unicode characters > ------------------------------------------------------------------------------------- > > Key: JBTM-1520 > URL: https://issues.jboss.org/browse/JBTM-1520 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Common > Affects Versions: 4.6.1.CP13 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 4.6.1.CP14 > > > If the path to arjuna configuration file contains unicode characters the XMLFilePlugin class fails to read it. XMLFilePlugin then calls DocumentBuilder#parse(String uri) which expects the argument being a valid URI. As long as URI spec does not support unicode chars the filename in XMLFilePlugin needs to be converted to a valid URI without any unicode/special characters. > Note that FileLocator.locateFile performs some conversions over the filename, but these do not seem to be enough. > This bug prevents Arjuna from starting which subsequently prevents EAP from starting. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1520) XMLFilePlugin fails to read the configuration if its path contains unicode characters

by Ivo Studensky (JIRA)

Ivo Studensky created JBTM-1520: ----------------------------------- Summary: XMLFilePlugin fails to read the configuration if its path contains unicode characters Key: JBTM-1520 URL: https://issues.jboss.org/browse/JBTM-1520 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Common Affects Versions: 4.6.1.CP13 Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: 4.6.1.CP14 If the path to arjuna configuration file contains unicode characters the XMLFilePlugin class fails to read it. XMLFilePlugin then calls DocumentBuilder#parse(String uri) which expects the argument being a valid URI. As long as URI spec does not support unicode chars the filename in XMLFilePlugin needs to be converted to a valid URI without any unicode/special characters. Note that FileLocator.locateFile performs some conversions over the filename, but these do not seem to be enough. This bug prevents Arjuna from starting which subsequently prevents EAP from starting. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1508) DisabledContextPropagationTest fails when standalone.xml content is updated by jboss-as

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1508?page=com.atlassian.jira.plugin.... ] Work on JBTM-1508 started by Gytis Trikleris. > DisabledContextPropagationTest fails when standalone.xml content is updated by jboss-as > --------------------------------------------------------------------------------------- > > Key: JBTM-1508 > URL: https://issues.jboss.org/browse/JBTM-1508 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.0.0.M2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Currently we copy across a modified version of standalone-xts.xml. The problem is that this file needs to be kept in sync with the original. > The main problem is that these tests will fail every time an upstream change is made to standalone-xts.xml. > This problem is related with com.arjuna.wstx.tests.arq.ba.DisabledContextPropagationTest, com.arjuna.wstx.tests.arq.basic.DisabledContextPropagationTest, and org.jboss.jbossts.txbridge.tests.outbound.junit.DisabledContextPropagationTests -- 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, 8 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 March 2013