November 2013 - jbossts-issues - Jboss List Archives

[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 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 ctomc. -- 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: ------------------------------------- The workaround looks acceptable. I don't know of a better approach. Can you raise this issue with Arquillian, so that we can remove the workaround in the future? > 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-2015) Update dependency versions and start using jboss-parent.

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2015: ------------------------------------- Summary: 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 -- 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)

Gytis Trikleris created JBTM-2014: ------------------------------------- Summary: 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. -- 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: ---------------------------------------- After changing the protocol to Servlet 3.0 I've started to struggle with JBTM-1128 and JBTM1217. It seems that all of this was a problem with Arquillian. I've changed the artifact arquilian container to 1.1.1.Final and it started to understand the jmx-as7 protocol (btw. the dependency to deployment.arquillian-service is not needed anymore). There was still a problem with IBM JDK and recovery tests. It seems that there could be some timing issue or the IBM JDK works differently in java.net.Socket class as controller.start receives exception from the ManagedDeployableContainer: http://grepcode.com/file/repo1.maven.org/maven2/org.jboss.as/jboss-as-arq... In fact the server is not started and I did a (bit nasty) workaround which check reason of the exception and in case that the server seems to be started it does not re-throw the arquillian LifeCycleException up. https://github.com/ochaloup/narayana/commit/8026b5243e3cb207d48474998eb0d... > 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-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 updated JBTM-2013: -------------------------------- Assignee: Amos Feng (was: Tom Jenkinson) > 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)

Tom Jenkinson created JBTM-2013: ----------------------------------- Summary: 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: Tom Jenkinson 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-2012) Initial value of MBean property ObjStoreBrowserMBean.exposeAllRecordsAsMBeans should be configurable

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2012?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2012: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Initial value of MBean property ObjStoreBrowserMBean.exposeAllRecordsAsMBeans should be configurable > ---------------------------------------------------------------------------------------------------- > > Key: JBTM-2012 > URL: https://issues.jboss.org/browse/JBTM-2012 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.17.16 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.16 > > > There is a JMX option on the ObjStoreBrowser MBean to tell it to expose all txn logs rather than the default well defined `safe` subset. The initial value should be configurable via ObjectStoreEnvironmentBean. -- 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-2012) Initial value of MBean property ObjStoreBrowserMBean.exposeAllRecordsAsMBeans should be configurable

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2012?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2012: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/523 > Initial value of MBean property ObjStoreBrowserMBean.exposeAllRecordsAsMBeans should be configurable > ---------------------------------------------------------------------------------------------------- > > Key: JBTM-2012 > URL: https://issues.jboss.org/browse/JBTM-2012 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.17.16 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.16 > > > There is a JMX option on the ObjStoreBrowser MBean to tell it to expose all txn logs rather than the default well defined `safe` subset. The initial value should be configurable via ObjectStoreEnvironmentBean. -- 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-2012) Initial value of MBean property ObjStoreBrowserMBean.exposeAllRecordsAsMBeans should be configurable

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2012: -------------------------------------- Summary: Initial value of MBean property ObjStoreBrowserMBean.exposeAllRecordsAsMBeans should be configurable Key: JBTM-2012 URL: https://issues.jboss.org/browse/JBTM-2012 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.17.16 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.17.16 There is a JMX option on the ObjStoreBrowser MBean to tell it to expose all txn logs rather than the default well defined `safe` subset. The initial value should be configurable via ObjectStoreEnvironmentBean. -- 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