November 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2014) Get rid of transitive Netty dependencies

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2014?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2014: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/524 > Get rid of transitive Netty dependencies > ---------------------------------------- > > Key: JBTM-2014 > URL: https://issues.jboss.org/browse/JBTM-2014 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.CR2 > > > There is a transitive Netty dependency which conflicts with the new HornetQ in Wildfly. Requested by Jean-Frederic Mesnil. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2014) Get rid of transitive Netty dependencies

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2014?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2014: ---------------------------------- Description: There is a transitive Netty dependency which conflicts with the new HornetQ in Wildfly. Requested by Jean-Frederic Mesnil. (was: There is a transitive Netty dependency which conflicts with the new HornetQ in Wildfly. Requested by jmesnil.) > Get rid of transitive Netty dependencies > ---------------------------------------- > > Key: JBTM-2014 > URL: https://issues.jboss.org/browse/JBTM-2014 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.CR2 > > > There is a transitive Netty dependency which conflicts with the new HornetQ in Wildfly. Requested by Jean-Frederic Mesnil. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2015) Update dependency versions and start using jboss-parent.

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2015?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2015: ---------------------------------- Description: Requested by Tomaz Cerar. (was: Requested by ctomc.) > Update dependency versions and start using jboss-parent. > -------------------------------------------------------- > > Key: JBTM-2015 > URL: https://issues.jboss.org/browse/JBTM-2015 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.CR2 > > > Requested by Tomaz Cerar. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2013) BlackTie Quickstarts not working on Taconic for CR1

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2013?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2013: ------------------------------------- The CR1 quickstarts do not work on my XP vm using the download from http://narayana.io//downloads/5_0_0_CR1 Unfortunately CI is down but my best guess is the ones on download are built using VC10 and (at least my VM) is using VC9 > BlackTie Quickstarts not working on Taconic for CR1 > --------------------------------------------------- > > Key: JBTM-2013 > URL: https://issues.jboss.org/browse/JBTM-2013 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator > Affects Versions: 5.0.0.CR1 > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.CR2 > > > All of the CR1-SNAPSHOT and now CR2-SNAPSHOT builds are fine, its just the CR1 tag for some reason. > http://172.17.131.2/view/Narayana+BlackTie-release/job/release-btny-naray... > Its possible a misconfiguration of the job or something to do with the version somehow. I get the same issue if I: > cd into the CI nodes checkout > cd into blacktie/dist/target/blacktie-5.0.0.CR1 > setenv > cd ../../../xatmi/fooapp > server -i 1 -s fooapp > As I say, CR2-SNAPSHOT is working fine so I suspect a misconfiguration -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2013) BlackTie Quickstarts not working on Taconic for CR1

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2013?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2013: ------------------------------------- The CR1 quickstarts work fine on my XP vm > BlackTie Quickstarts not working on Taconic for CR1 > --------------------------------------------------- > > Key: JBTM-2013 > URL: https://issues.jboss.org/browse/JBTM-2013 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator > Affects Versions: 5.0.0.CR1 > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.CR2 > > > All of the CR1-SNAPSHOT and now CR2-SNAPSHOT builds are fine, its just the CR1 tag for some reason. > http://172.17.131.2/view/Narayana+BlackTie-release/job/release-btny-naray... > Its possible a misconfiguration of the job or something to do with the version somehow. I get the same issue if I: > cd into the CI nodes checkout > cd into blacktie/dist/target/blacktie-5.0.0.CR1 > setenv > cd ../../../xatmi/fooapp > server -i 1 -s fooapp > As I say, CR2-SNAPSHOT is working fine so I suspect a misconfiguration -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1957) XTS crash recovery tests fail on IBM JDK

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-1957?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka commented on JBTM-1957: ---------------------------------------- Yeap, it's OK. I'll try to create a simple reproducer if possible and I'll let you know. Anyhow I suppose that it's late to do any changes to codebase for current EAP6 release. For the moment I will create a patch and apply it for the testing. Thanks > XTS crash recovery tests fail on IBM JDK > ---------------------------------------- > > Key: JBTM-1957 > URL: https://issues.jboss.org/browse/JBTM-1957 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.10 > Reporter: Ondřej Chaloupka > Assignee: Ondřej Chaloupka > Priority: Minor > > The XTS crash recovery tests fail on IBM JDK. This seem to be a problem of Arquillian settings. > What I do: > - switch to IBM JDK (JAVA_HOME + PATH) > - export JBOSS_HOME=/home/ochaloup/jboss/jboss-eap-* > - cd XTS/localjunit/crash-recovery-tests > - mvn test -Pxts.integration.tests.profile -Parq -Dtest=com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit > What I get - tests fail with error: > The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1957) XTS crash recovery tests fail on IBM JDK

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1957?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1957: ------------------------------------- I guess the best thing is to make sure we have raised the ARQ issue (with simplified test case) to eliminate any possibility that it is an issue in our test. Then we can link that Jira to this one. We can then resolve this issue, and create a new one to "Remove workaround for JBTM-1957" which links to this issue and probably the ARQ one too. Is that OK? > XTS crash recovery tests fail on IBM JDK > ---------------------------------------- > > Key: JBTM-1957 > URL: https://issues.jboss.org/browse/JBTM-1957 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.10 > Reporter: Ondřej Chaloupka > Assignee: Ondřej Chaloupka > Priority: Minor > > The XTS crash recovery tests fail on IBM JDK. This seem to be a problem of Arquillian settings. > What I do: > - switch to IBM JDK (JAVA_HOME + PATH) > - export JBOSS_HOME=/home/ochaloup/jboss/jboss-eap-* > - cd XTS/localjunit/crash-recovery-tests > - mvn test -Pxts.integration.tests.profile -Parq -Dtest=com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit > What I get - tests fail with error: > The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1957) XTS crash recovery tests fail on IBM JDK

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1957?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1957: ------------------------------------- I agree that the fix in Arquillian is preferable. However, this is an EAP 6 fix, so I'm not sure we will be able to get the fix worked in in-time. > XTS crash recovery tests fail on IBM JDK > ---------------------------------------- > > Key: JBTM-1957 > URL: https://issues.jboss.org/browse/JBTM-1957 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.10 > Reporter: Ondřej Chaloupka > Assignee: Ondřej Chaloupka > Priority: Minor > > The XTS crash recovery tests fail on IBM JDK. This seem to be a problem of Arquillian settings. > What I do: > - switch to IBM JDK (JAVA_HOME + PATH) > - export JBOSS_HOME=/home/ochaloup/jboss/jboss-eap-* > - cd XTS/localjunit/crash-recovery-tests > - mvn test -Pxts.integration.tests.profile -Parq -Dtest=com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit > What I get - tests fail with error: > The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1957) XTS crash recovery tests fail on IBM JDK

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1957?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1957: ------------------------------------- Hi Ondra, I think we should raise an Arquillian issue rather than the workaround, is that possible? It should be quite straight forward to create a simple Arquillian test that just starts the server to replicate this. "Server is already running" can be quite a common issue, to start masking that would not be perfect. Even though your wasStarted check does eliminate some possibilities, I would have to defer to Paul on whether it is too much of a catchall solution. Also, how come you externalised the "jboss-as" variable. I agree its nicer in a variable but it makes the diff more involved. Tom > XTS crash recovery tests fail on IBM JDK > ---------------------------------------- > > Key: JBTM-1957 > URL: https://issues.jboss.org/browse/JBTM-1957 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.10 > Reporter: Ondřej Chaloupka > Assignee: Ondřej Chaloupka > Priority: Minor > > The XTS crash recovery tests fail on IBM JDK. This seem to be a problem of Arquillian settings. > What I do: > - switch to IBM JDK (JAVA_HOME + PATH) > - export JBOSS_HOME=/home/ochaloup/jboss/jboss-eap-* > - cd XTS/localjunit/crash-recovery-tests > - mvn test -Pxts.integration.tests.profile -Parq -Dtest=com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit > What I get - tests fail with error: > The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2014) Get rid of transitive Netty dependencies

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2014?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2014: ---------------------------------- Description: There is a transitive Netty dependency which conflicts with the new HornetQ in Wildfly. Requested by jmesnil. (was: There is a transitive Netty dependency which conflicts with the new HornetQ in Wildfly.) > Get rid of transitive Netty dependencies > ---------------------------------------- > > Key: JBTM-2014 > URL: https://issues.jboss.org/browse/JBTM-2014 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.CR2 > > > There is a transitive Netty dependency which conflicts with the new HornetQ in Wildfly. Requested by jmesnil. -- 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

12 years, 5 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 November 2013