February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1470) hudson build script copies over the wrong integration jar

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1470?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-1470. ------------------------------------ Resolution: Done resolved by pull https://github.com/jbosstm/narayana/pull/221 (commit 6c5cd835a431c6d67512743487aeb178f706f957) > hudson build script copies over the wrong integration jar > --------------------------------------------------------- > > Key: JBTM-1470 > URL: https://issues.jboss.org/browse/JBTM-1470 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 5.0.0.M2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M2 > > > The JIRA is low priority because it does not effect CI builds. > scripts/hudson/narayana.sh has a variable called BUILD_AS. If this is set to zero then the AS will not be built but after a narayana build the script will copy over the final jts jars to the AS modules folder (provided the AS directory is present) - this feature is useful for developer testing to avoid a full rebuild of the AS). There are 2 bugs: > - the name is still referring to the old jbossjts.XXX.jar name > - the jars should only be copied if BUILD_AS is set to zero > Note that other subsystem jars generated by a narayana build (such as xts) are not copied over. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1313) Performance related work that involves other products should be in a separate repository

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1313?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1313: ----------------------------------- Original Estimate: 2 days Remaining Estimate: 2 days > Performance related work that involves other products should be in a separate repository > ------------------------------------------------------------------------------------------ > > Key: JBTM-1313 > URL: https://issues.jboss.org/browse/JBTM-1313 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, Performance Testing > Affects Versions: 5.0.0.M1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M2 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Any performance related activities done by the dev team that require installation of other transaction managers should done a repo that is separate from the main narayana repo. Currently this includes: > - some changes to the jts quickstart > - the performance harness in qa/tests/product -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1313) Performance related work that involves other products should be in a separate repository

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1313?page=com.atlassian.jira.plugin.... ] Work on JBTM-1313 started by Michael Musgrove. > Performance related work that involves other products should be in a separate repository > ------------------------------------------------------------------------------------------ > > Key: JBTM-1313 > URL: https://issues.jboss.org/browse/JBTM-1313 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, Performance Testing > Affects Versions: 5.0.0.M1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M2 > > > Any performance related activities done by the dev team that require installation of other transaction managers should done a repo that is separate from the main narayana repo. Currently this includes: > - some changes to the jts quickstart > - the performance harness in qa/tests/product -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?focusedWorklogId=12428709&page=c... ] Gytis Trikleris logged work on JBTM-986: ---------------------------------------- Author: Gytis Trikleris Created on: 18/Feb/13 6:02 PM Start Date: 18/Feb/13 6:00 AM Worklog Time Spent: 5 hours Issue Time Tracking ------------------- Remaining Estimate: 3 hours (was: 1 day) Time Spent: 1 week, 2 days, 3 hours (was: 1 week, 1 day, 6 hours) Worklog Id: (was: 12428709) > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Time Spent: 1 week, 2 days, 3 hours > Remaining Estimate: 3 hours > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. > We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > The feature should be "enabled" by default providing the feature is enabled in the XTS server config. > The quickstarts also need updated to use this. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1143) Narayana with Maven Central

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1143?page=com.atlassian.jira.plugin.... ] Work on JBTM-1143 started by Paul Robinson. > Narayana with Maven Central > --------------------------- > > Key: JBTM-1143 > URL: https://issues.jboss.org/browse/JBTM-1143 > 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 > > Original Estimate: 4 hours > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Try syncing from M1 onwards, so that it will be synced immediately after M2 is released. > We should also take a look at what things we depend on that are not in maven central. I said that I would take steps to reduce the number of these. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1440) Move the XTS documentation into the /docs folder

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1440?page=com.atlassian.jira.plugin.... ] Work on JBTM-1440 started by Paul Robinson. > Move the XTS documentation into the /docs folder > ------------------------------------------------ > > Key: JBTM-1440 > URL: https://issues.jboss.org/browse/JBTM-1440 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, XTS > Affects Versions: 4.17.3 > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 1 day > Time Spent: 1 hour > Remaining Estimate: 7 hours > > It appears that there is no need to split the documentation between community/product, see JBTM-835 for details. It may be worth double checking it is all still product related, if not, leave some in XTS/docs and move the relevant parts into /docs/XTS? > We should also use this as an opportunity to check that the docs are current. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1440) Move the XTS documentation into the /docs folder

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1440?focusedWorklogId=12428707&page=... ] Paul Robinson logged work on JBTM-1440: --------------------------------------- Author: Paul Robinson Created on: 18/Feb/13 1:13 PM Start Date: 18/Feb/13 1:13 PM Worklog Time Spent: 1 hour Issue Time Tracking ------------------- Remaining Estimate: 7 hours (was: 1 day) Time Spent: 1 hour Worklog Id: (was: 12428707) > Move the XTS documentation into the /docs folder > ------------------------------------------------ > > Key: JBTM-1440 > URL: https://issues.jboss.org/browse/JBTM-1440 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, XTS > Affects Versions: 4.17.3 > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 1 day > Time Spent: 1 hour > Remaining Estimate: 7 hours > > It appears that there is no need to split the documentation between community/product, see JBTM-835 for details. It may be worth double checking it is all still product related, if not, leave some in XTS/docs and move the relevant parts into /docs/XTS? > We should also use this as an opportunity to check that the docs are current. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1440) Move the XTS documentation into the /docs folder

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1440?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1440: ------------------------------------- Moved the docs, now reading through the doc now checking for non-product related material and for general correctness. Using this branch: https://github.com/paulrobinson/documentation/tree/master-JBTM-1440_Move_... > Move the XTS documentation into the /docs folder > ------------------------------------------------ > > Key: JBTM-1440 > URL: https://issues.jboss.org/browse/JBTM-1440 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, XTS > Affects Versions: 4.17.3 > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > It appears that there is no need to split the documentation between community/product, see JBTM-835 for details. It may be worth double checking it is all still product related, if not, leave some in XTS/docs and move the relevant parts into /docs/XTS? > We should also use this as an opportunity to check that the docs are current. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1475) TXBridge InboundCrashRecoveryTests failure - could not start container

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1475?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1475: ------------------------------------- Nothing obvious, waiting to see if it happens again. > TXBridge InboundCrashRecoveryTests failure - could not start container > ---------------------------------------------------------------------- > > Key: JBTM-1475 > URL: https://issues.jboss.org/browse/JBTM-1475 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M2 > > > See: http://172.17.131.2/job/narayana-dualstack/83 > {noformat} > Tests in error: > testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Could not start container > testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Deployment with name txbridge-inbound-tests-client could not be undeployed. Container jboss must be still running. > {noformat} -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1475) TXBridge InboundCrashRecoveryTests failure - could not start container

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1475?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1475: ------------------------------------- Other than the above Exception, the server seems to start up without issue in a timely mannor. The test log states that the server didn't start within 60s, but looking at the four server starts in the log they all started in 20s or under. > TXBridge InboundCrashRecoveryTests failure - could not start container > ---------------------------------------------------------------------- > > Key: JBTM-1475 > URL: https://issues.jboss.org/browse/JBTM-1475 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M2 > > > See: http://172.17.131.2/job/narayana-dualstack/83 > {noformat} > Tests in error: > testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Could not start container > testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Deployment with name txbridge-inbound-tests-client could not be undeployed. Container jboss must be still running. > {noformat} -- 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

13 years, 1 month

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 February 2013