May 2013 - jbossts-issues - Jboss List Archives

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

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1693?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1693: -------------------------------- Summary: Arquillian DeploymentException: Cannot deploy: test.war (was: TXFramework Tests: Arquillian DeploymentException: Cannot deploy: test.war) > 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-1691) Auto-merge in narayana.sh is not robust enough

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1691?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1691: ------------------------------------- Can you clarify why we would need to update version.org.jboss.jboss-vfs in the 5_BRANCH? > Auto-merge in narayana.sh is not robust enough > ---------------------------------------------- > > Key: JBTM-1691 > URL: https://issues.jboss.org/browse/JBTM-1691 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.M3 > > > This can't be auto=merged: > {code} > <<<<<<< HEAD > <version.org.jboss.jbossts.jbossjts>5.0.0.M2</version.org.jboss.jbossts.jbossjts> > <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M2</version.org.jboss.jbossts.jbossjts-integration> > <version.org.jboss.jbossts.jbossxts>5.0.0.M2</version.org.jboss.jbossts.jbossxts> > <version.org.jboss.jboss-vfs>3.2.0.Beta1</version.org.jboss.jboss-vfs> > <version.org.jboss.jbossts.narayana>5.0.0.M2</version.org.jboss.jbossts.narayana> > ======= > <version.org.jboss.jbossts.jbossjts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts> > <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts-integration> > <version.org.jboss.jbossts.jbossxts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossxts> > <version.org.jboss.jboss-vfs>3.1.0.Final</version.org.jboss.jboss-vfs> > <version.org.jboss.jbossts.narayana>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.narayana> > >>>>>>> Upgrade Narayana to 5.0.0.M3-SNAPSHOT > {code} > Our current strategy will take our version which results in the old version of jboss-vfs being used, which in turn causes a build failure in WildFly. > Maybe we should remove the auto-merge and replace with a manual intervention when a conflict occurs? -- 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 Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1695?page=com.atlassian.jira.plugin.... ] Paul Robinson edited comment on JBTM-1695 at 5/20/13 7:42 AM: -------------------------------------------------------------- It's not just for familiarity. It also makes the history a lot harder to navigate, if you re-name the directory structure. was (Author: paul.robinson): It's not just for familiarity. It also makes the history a lot harder to navigate. > 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-1695) Change the 'common' module to use the normal maven convention for source layout.

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1695?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1695: ------------------------------------- It's not just for familiarity. It also makes the history a lot harder to navigate. > 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-1689) "jta" vs. "jts" profile seems duplicate

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1689?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1689: ------------------------------------- Good point, it is even simpler than that using -am (also make), you don't need to list the dependencies: mvn -pl ArjunaCore/arjunacore -am Feel free to raise a PR to remove the redundant profiles > "jta" vs. "jts" profile seems duplicate > --------------------------------------- > > Key: JBTM-1689 > URL: https://issues.jboss.org/browse/JBTM-1689 > 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: Tom Jenkinson > Priority: Minor > > "jta" vs. "jts" profile, they seem to build the same modules except for ArjunaJTS. > As maven has some built in options for selecting which modules/directories to build, would it be better to just use those options? Instead of defining profiles, it might look something like "mvn install -pl common,ArjunaCore" instead of the build profile "mvn install -Pcore" -- 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-1694) upload orson and emma to repository.jboss.org

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1694?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1694: -------------------------------- Fix Version/s: 5.0.0.M3 > upload orson and emma to repository.jboss.org > --------------------------------------------- > > Key: JBTM-1694 > URL: https://issues.jboss.org/browse/JBTM-1694 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Weinan Li > Assignee: Tom Jenkinson > Fix For: 5.0.0.M3 > > > Currently in ArjunaCore/arjuna/pom.xml: > {code} > <systemPath>${orson.jar.location}/../qa/dbdrivers/jConnect-6_0/classes/jconn3.jar</systemPath> > {code} > And user need to download orson.jar from internet and set orson jar location manually. Is it okay that we upload the jars to repository.jboss.org? -- 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 Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1695?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1695: ------------------------------------- Hi Weinan, It wasn't so much for compatibility, what I meant is we actively intended to leave the folders where they were in order that people familiar with the project could locate the components that they were used to. I am happy to change this structure (new components use standard maven layout), however I would prefer to do this _only_ if there is an actual technical issue with productization if you see what I mean (i.e. really this means if you are required to patch around it somehow). Our support engineers for example are familiar with the current structure. Thanks! Tom > 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-1694) upload orson and emma to repository.jboss.org

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1694?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1694: -------------------------------- Fix Version/s: 4.17.5 > upload orson and emma to repository.jboss.org > --------------------------------------------- > > Key: JBTM-1694 > URL: https://issues.jboss.org/browse/JBTM-1694 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Weinan Li > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.M3 > > > Currently in ArjunaCore/arjuna/pom.xml: > {code} > <systemPath>${orson.jar.location}/../qa/dbdrivers/jConnect-6_0/classes/jconn3.jar</systemPath> > {code} > And user need to download orson.jar from internet and set orson jar location manually. Is it okay that we upload the jars to repository.jboss.org? -- 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 Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1697?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1697: ------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64-el5/1534/ > 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-1694) upload orson and emma to repository.jboss.org

by Weinan Li (JIRA)

[ https://issues.jboss.org/browse/JBTM-1694?page=com.atlassian.jira.plugin.... ] Weinan Li commented on JBTM-1694: --------------------------------- The solution looks good :-) Thanks for help! > upload orson and emma to repository.jboss.org > --------------------------------------------- > > Key: JBTM-1694 > URL: https://issues.jboss.org/browse/JBTM-1694 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Weinan Li > Assignee: Tom Jenkinson > > Currently in ArjunaCore/arjuna/pom.xml: > {code} > <systemPath>${orson.jar.location}/../qa/dbdrivers/jConnect-6_0/classes/jconn3.jar</systemPath> > {code} > And user need to download orson.jar from internet and set orson jar location manually. Is it okay that we upload the jars to repository.jboss.org? -- 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