May 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1699) Changes to the transaction SPI

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1699: -------------------------------------- Summary: Changes to the transaction SPI Key: JBTM-1699 URL: https://issues.jboss.org/browse/JBTM-1699 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Application Server Integration Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.0.Final wildfly is using a number of our internal com.arjuna interfaces which we would like to resolve by providing the same functionality in the transactions SPI. Additionally the current SPI contains a number of unused classes which need removing. I have created https://github.com/jbosstm/jboss-transaction-spi to manage the changes. To avoid any potential confusion and to make it clear who is responsible for the SPI we will be changing the package names. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1698) Make commit response body optional

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1698: ------------------------------------- Summary: Make commit response body optional Key: JBTM-1698 URL: https://issues.jboss.org/browse/JBTM-1698 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Components: REST Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.0.0.Final If commit response body is empty but status=200, transaction should still be committed successfully. See: RESTRecord.doCommit -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1693) TXFramework Tests: Arquillian DeploymentException: Cannot deploy: test.war

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1693?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1693: --------------------------------- yeah, I'm testing on the local machine to make sure all tests work fine. > TXFramework Tests: Arquillian DeploymentException: Cannot deploy: test.war > -------------------------------------------------------------------------- > > Key: JBTM-1693 > URL: https://issues.jboss.org/browse/JBTM-1693 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > See: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/48/TESTS=XTS,jdk=... > Looks like a general issue with our usage of Arquillian. It seems to be happening consistently, so should be easy to reproduce. It's just started happening and I don't think we have made any changes that could of caused it, therefore I suspect it's due to some change in WildFly. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1693) TXFramework Tests: Arquillian DeploymentException: Cannot deploy: test.war

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1693?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1693: ------------------------------------- Great, thanks for figuring it out. Can you ensure your pull request updates all occurrences of 'jboss-as-arquillian-container-managed' as this is going to effect all tests that use Arquillian. > TXFramework Tests: Arquillian DeploymentException: Cannot deploy: test.war > -------------------------------------------------------------------------- > > Key: JBTM-1693 > URL: https://issues.jboss.org/browse/JBTM-1693 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > See: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/48/TESTS=XTS,jdk=... > Looks like a general issue with our usage of Arquillian. It seems to be happening consistently, so should be easy to reproduce. It's just started happening and I don't think we have made any changes that could of caused it, therefore I suspect it's due to some change in WildFly. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1693) TXFramework Tests: Arquillian DeploymentException: Cannot deploy: test.war

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1693?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1693: --------------------------------- jboss-as-arquillian-container-managed should be changed to wildfly-arquillian-container-managed > TXFramework Tests: Arquillian DeploymentException: Cannot deploy: test.war > -------------------------------------------------------------------------- > > Key: JBTM-1693 > URL: https://issues.jboss.org/browse/JBTM-1693 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > See: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/48/TESTS=XTS,jdk=... > Looks like a general issue with our usage of Arquillian. It seems to be happening consistently, so should be easy to reproduce. It's just started happening and I don't think we have made any changes that could of caused it, therefore I suspect it's due to some change in WildFly. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1697) AdvertiseUnadvertiseTest failed with could not deploy queue of .testsui1

by Amos Feng (JIRA)

Amos Feng created JBTM-1697: ------------------------------- Summary: AdvertiseUnadvertiseTest failed with could not deploy queue of .testsui1 Key: JBTM-1697 URL: https://issues.jboss.org/browse/JBTM-1697 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: BlackTie Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.0.0.M3 http://172.17.131.2/job/blacktie-linux64-el5/1528/ {noformat} 06:38:31,520 INFO [AdvertiseUnadvertiseTest] (default task-2) Got the exception 06:38:31,872 ERROR [org.jboss.remoting.remote.connection] (Remoting "beacon:MANAGEMENT" I/O-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856 06:38:32,400 INFO [org.hornetq.ra] (default-threads - 1) HQ151001: Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@2c717166 destination=queue/BTR_BTStompAdmin destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15) 06:38:36,876 ERROR [org.jboss.narayana.blacktie.administration.BlacktieStompAdministrationService] (default task-2) Could not deploy queue of .testsui1: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9999. The connection timed out {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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1695) Change the 'common' module to use the normal maven convention for source layout.

by Weinan Li (JIRA)

[ https://issues.jboss.org/browse/JBTM-1695?page=com.atlassian.jira.plugin.... ] Weinan Li updated JBTM-1695: ---------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/294 > Change the 'common' module to use the normal maven convention for source layout. > -------------------------------------------------------------------------------- > > Key: JBTM-1695 > URL: https://issues.jboss.org/browse/JBTM-1695 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Weinan Li > > The common module doesn't use the normal maven convention for source layout. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1696) arjunacore: artifactId is "arjunacore-all" but the name of the project is "ArjunaCore everything"

by Weinan Li (JIRA)

[ https://issues.jboss.org/browse/JBTM-1696?page=com.atlassian.jira.plugin.... ] Weinan Li updated JBTM-1696: ---------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/293 > arjunacore: artifactId is "arjunacore-all" but the name of the project is "ArjunaCore everything" > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1696 > URL: https://issues.jboss.org/browse/JBTM-1696 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Weinan Li > Priority: Minor > > arjunacore: artifactId is "arjunacore-all" but the name of the project is "ArjunaCore everything". it doesn't seem like a big issue, but when you are trying to track down a build failure, and you see the project name, it doesn't help you figure out where the failing code is. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1696) arjunacore: artifactId is "arjunacore-all" but the name of the project is "ArjunaCore everything"

by Weinan Li (JIRA)

Weinan Li created JBTM-1696: ------------------------------- Summary: arjunacore: artifactId is "arjunacore-all" but the name of the project is "ArjunaCore everything" Key: JBTM-1696 URL: https://issues.jboss.org/browse/JBTM-1696 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Affects Versions: 4.17.4 Reporter: Weinan Li Assignee: Weinan Li Priority: Minor arjunacore: artifactId is "arjunacore-all" but the name of the project is "ArjunaCore everything". it doesn't seem like a big issue, but when you are trying to track down a build failure, and you see the project name, it doesn't help you figure out where the failing code is. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1695) Change the 'common' module to use the normal maven convention for source layout.

by Weinan Li (JIRA)

Weinan Li created JBTM-1695: ------------------------------- Summary: Change the 'common' module to use the normal maven convention for source layout. Key: JBTM-1695 URL: https://issues.jboss.org/browse/JBTM-1695 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.17.4 Reporter: Weinan Li Assignee: Weinan Li The common module doesn't use the normal maven convention for source layout. -- 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, 6 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 May 2013