January 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1434) During CI Only install artifacts to local .m2 repo that will be uploaded to Nexus during release

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1434?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1434: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/213 > During CI Only install artifacts to local .m2 repo that will be uploaded to Nexus during release > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1434 > URL: https://issues.jboss.org/browse/JBTM-1434 > Project: JBoss Transaction Manager > Issue Type: Bug > 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 > Remaining Estimate: 4 hours > > Apply JBTM-1307 to 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1424) Remove static block from org.jboss.jbossts.xts.environment.XTSPropertyManager

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1424?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1424: ------------------------------------- Shouldn't this also be fixed for 4.17? > Remove static block from org.jboss.jbossts.xts.environment.XTSPropertyManager > ----------------------------------------------------------------------------- > > Key: JBTM-1424 > URL: https://issues.jboss.org/browse/JBTM-1424 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > Original Estimate: 10 minutes > Time Spent: 10 minutes > Remaining Estimate: 0 minutes > > Where it catches an exception in the static block and then just uses system properties. I would say that behavior would be better encapsulated in XTSPropertiesFactory.getDefaultProperties itself (thereby removing another static block and making XTSPropertiesFactory.getDefaultProperties more stable). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1434) During CI Only install artifacts to local .m2 repo that will be uploaded to Nexus during release

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1434?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1434: -------------------------------- Description: Apply JBTM-1307 to master. (was: Apply JBTM-1306 to master.) > During CI Only install artifacts to local .m2 repo that will be uploaded to Nexus during release > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1434 > URL: https://issues.jboss.org/browse/JBTM-1434 > Project: JBoss Transaction Manager > Issue Type: Bug > 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 > Remaining Estimate: 4 hours > > Apply JBTM-1307 to 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1434) During CI Only install artifacts to local .m2 repo that will be uploaded to Nexus during release

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1434?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1434: -------------------------------- Summary: During CI Only install artifacts to local .m2 repo that will be uploaded to Nexus during release (was: Multiple JBossTS poms released to nexus contain missing dependencies) > During CI Only install artifacts to local .m2 repo that will be uploaded to Nexus during release > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1434 > URL: https://issues.jboss.org/browse/JBTM-1434 > Project: JBoss Transaction Manager > Issue Type: Bug > 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 > Remaining Estimate: 4 hours > > Apply JBTM-1306 to 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1382) QA build does not archive test group summary files

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1382?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1382: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done The zip pattern is "testoutput/**,TEST* > QA build does not archive test group summary files > -------------------------------------------------- > > Key: JBTM-1382 > URL: https://issues.jboss.org/browse/JBTM-1382 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The QA test suite consists of a number of test groups. The build produces a summary file showing the status of each sub test within a group (these are called TEST-<test group>.txt and stored in the qa directory). We currently archive the qa/testoutput directory but it would be useful to also archive these summary text files. Note that we cannot rely on Jenkins to do this for us since the jts remote test group is executed twice (once for each orb) and the files from the first run are overwritten. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1398: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M2) > Review subsystem usage across Narayana > -------------------------------------- > > Key: JBTM-1398 > URL: https://issues.jboss.org/browse/JBTM-1398 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > Original Estimate: 2 days > Time Spent: 1 day, 7 hours > Remaining Estimate: 2 days, 6 hours > > h2. Components and their subsystem requirements: > h5. Transactions > * To Investigate > > h5. XTS > * Bootstrap coordinator > * Setup WS endpoints for coordinator > * Setup WS endpoints for the participants > * Respond to configuration from standalone-xts.xml > h5. REST-TX > * Boostrap the coordinator > * Setup a REST endpoint for the coordinator > * Setup a REST endpoint for the participants > h5. Blacktie > * Register MDB > * Register MBean > h5. STM > * To Investigate > h5. TXF > * Modify the WS handler chain on application deployment > * Registers a CDI extension > h2. Notable Dependencies > h5. TXF > * Weld -> EJB3 -> Transactions (Could check that each link is valid. Check if subsys or regular dep) > * JBossWS. Might be able to remove by putting the WS specific stuff into the XTS subsystem. > h2. Subsystem Breakdown > Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems. > h5. Transactions > * All current stuff > * STM > * TXF (Unlikely to work due to dependency on Weld for loading a portable extension) > h5. XTS > * All Current Stuff > h5. RTS (new) > h5. Blacktie (new) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1398: ------------------------------------- Pushing this back to 5.Final as the decision to have a TXF in it's own subsystem or combined with Transactions, will not impact the community using M2. If we decide to add configuration to TXF, we will then need to think about this as the configuration is located under the subsystem section of the standalone-*.xml We will need to address this before Narayana 5.x is merged into AS7, as they are unlikely to want an explosion in the number of subsystems. > Review subsystem usage across Narayana > -------------------------------------- > > Key: JBTM-1398 > URL: https://issues.jboss.org/browse/JBTM-1398 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 2 days > Time Spent: 1 day, 7 hours > Remaining Estimate: 2 days, 6 hours > > h2. Components and their subsystem requirements: > h5. Transactions > * To Investigate > > h5. XTS > * Bootstrap coordinator > * Setup WS endpoints for coordinator > * Setup WS endpoints for the participants > * Respond to configuration from standalone-xts.xml > h5. REST-TX > * Boostrap the coordinator > * Setup a REST endpoint for the coordinator > * Setup a REST endpoint for the participants > h5. Blacktie > * Register MDB > * Register MBean > h5. STM > * To Investigate > h5. TXF > * Modify the WS handler chain on application deployment > * Registers a CDI extension > h2. Notable Dependencies > h5. TXF > * Weld -> EJB3 -> Transactions (Could check that each link is valid. Check if subsys or regular dep) > * JBossWS. Might be able to remove by putting the WS specific stuff into the XTS subsystem. > h2. Subsystem Breakdown > Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems. > h5. Transactions > * All current stuff > * STM > * TXF (Unlikely to work due to dependency on Weld for loading a portable extension) > h5. XTS > * All Current Stuff > h5. RTS (new) > h5. Blacktie (new) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1344) org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1344?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1344: -------------------------------- Component/s: Testing > org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins) > ------------------------------------------------------------------------------------ > > Key: JBTM-1344 > URL: https://issues.jboss.org/browse/JBTM-1344 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TxBridge > Affects Versions: 4.17.3 > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 2 days > Time Spent: 1 hour, 30 minutes > Remaining Estimate: 1 day, 6 hours, 30 minutes > > See: http://172.17.131.2/job/jbossts-narayana-java6/81/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1382) QA build does not archive test group summary files

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1382?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1382: ----------------------------------- Original Estimate: 30 minutes (was: 4 hours) Remaining Estimate: 30 minutes (was: 4 hours) > QA build does not archive test group summary files > -------------------------------------------------- > > Key: JBTM-1382 > URL: https://issues.jboss.org/browse/JBTM-1382 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The QA test suite consists of a number of test groups. The build produces a summary file showing the status of each sub test within a group (these are called TEST-<test group>.txt and stored in the qa directory). We currently archive the qa/testoutput directory but it would be useful to also archive these summary text files. Note that we cannot rely on Jenkins to do this for us since the jts remote test group is executed twice (once for each orb) and the files from the first run are overwritten. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1422) Deployment failure because of missing service dependencies

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1422?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1422: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M2) > Deployment failure because of missing service dependencies > ---------------------------------------------------------- > > Key: JBTM-1422 > URL: https://issues.jboss.org/browse/JBTM-1422 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > > See: http://172.17.131.2/job/narayana/141 > {noformat} > org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase Time elapsed: 16103 sec <<< ERROR! > org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: wsba-participant-completion.war > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83) > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64) > ... > Caused by: java.lang.Exception: { > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.module.service.\"deployment.wsba-participant-completion.war\".main is missing [jboss.module.spec.service.\"deployment.arquillian-service\".main]"], > "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => { > "Services that were unable to start:" => ["jboss.deployment.unit.\"wsba-participant-completion.war\".FIRST_MODULE_USE"], > "Services that may be the cause:" => [ > "jboss.module.spec.service.\"deployment.arquillian-service\".main", > "jboss.txn.TransactionSynchronizationRegistry", > "jboss.txn.UserTransactionRegistry" > ] > } > } > ... > {noformat} > {noformat} > org.jboss.as.test.xts.simple.wsat.client.WSATTestCase Time elapsed: 1846 sec <<< ERROR! > org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: wsat.war > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83) > ... > Caused by: java.lang.Exception: { > "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.module.service.\"deployment.wsat.war\".main is missing [jboss.module.spec.service.\"deployment.arquillian-service\".main]"], > "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => { > "Services that were unable to start:" => ["jboss.deployment.unit.\"wsat.war\".FIRST_MODULE_USE"], > "Services that may be the cause:" => [ > "jboss.module.spec.service.\"deployment.arquillian-service\".main", > "jboss.txn.TransactionSynchronizationRegistry", > "jboss.txn.UserTransactionRegistry" > ] > } > } > ... > {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, 2 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 January 2013