November 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1838) Document how to configure XTS to use SSL

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1838?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1838: ----------------------------------- Fix Version/s: 4.17.17 (was: 4.17.16) > Document how to configure XTS to use SSL > ---------------------------------------- > > Key: JBTM-1838 > URL: https://issues.jboss.org/browse/JBTM-1838 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.CR2, 4.17.17 > > Original Estimate: 1 day > Time Spent: 1 day > Remaining Estimate: 4 hours > > The documentation should show how to use 'https' for all communications. > I'm not sure what form the documentation should take. Given that the majority of configuration is actually related to enabling SSL for Web Services in general, I don't think it should all live in the XTS docs. Maybe we just add the XTS specific stuff there and link to the docs on how to enable SSL for WS. > We could also provide a JDF quickstart. However, the docs comprise of many bash commands, so this may not fit in well with a quickstart. > Other options are a community wiki page or blog posting. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1838) Document how to configure XTS to use SSL

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1838?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1838: ---------------------------------- Fix Version/s: 5.0.0.CR2 (was: 5.0.0.M9) > Document how to configure XTS to use SSL > ---------------------------------------- > > Key: JBTM-1838 > URL: https://issues.jboss.org/browse/JBTM-1838 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 4.17.16, 5.0.0.CR2 > > Original Estimate: 1 day > Time Spent: 1 day > Remaining Estimate: 4 hours > > The documentation should show how to use 'https' for all communications. > I'm not sure what form the documentation should take. Given that the majority of configuration is actually related to enabling SSL for Web Services in general, I don't think it should all live in the XTS docs. Maybe we just add the XTS specific stuff there and link to the docs on how to enable SSL for WS. > We could also provide a JDF quickstart. However, the docs comprise of many bash commands, so this may not fit in well with a quickstart. > Other options are a community wiki page or blog posting. -- 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

10 years, 6 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: ---------------------------------------- OK, there is a problem... After changing the protocol to Servlet 3.0 I'm hitting the JBTM-1128 issue for crash recovery tests. > 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

10 years, 6 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: ---------------------------------------- I've found out that it's problem of set protocal type in the arquillian.xml file(s) and the problem can be hit just for EAP. The test uses jmx-as7 protocol which is not supported by EAP (currently). You need to change the protocol type to "Servlet 3.0" for test to work. > 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

10 years, 6 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 updated JBTM-1957: ----------------------------------- Priority: Minor (was: Major) > 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2011) TXFramework and XTS QS link to Beta1-SNAPSHOT of WildFly - needs to be Beta2

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2011?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2011: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TXFramework and XTS QS link to Beta1-SNAPSHOT of WildFly - needs to be Beta2 > ---------------------------------------------------------------------------- > > Key: JBTM-2011 > URL: https://issues.jboss.org/browse/JBTM-2011 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M9 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-quickstarts/35/co... > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 29.680s > [INFO] Finished at: Wed Nov 06 09:17:00 GMT 2013 > [INFO] Final Memory: 39M/94M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project non-transactional-resource-all: Could not resolve dependencies for project org.jboss.narayana.quickstart.xts.non-transactional-resource:non-transactional-resource-all:jar:5.0.0.M9-SNAPSHOT: Could not find artifact org.wildfly:wildfly-arquillian-container-managed:jar:8.0.0.Beta1-SNAPSHOT -> [Help 1] > [ERROR] > {code} -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2011) TXFramework and XTS QS link to Beta1-SNAPSHOT of WildFly - needs to be Beta2

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2011?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2011: -------------------------------- Description: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-quickstarts/35/co... {code} [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 29.680s [INFO] Finished at: Wed Nov 06 09:17:00 GMT 2013 [INFO] Final Memory: 39M/94M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project non-transactional-resource-all: Could not resolve dependencies for project org.jboss.narayana.quickstart.xts.non-transactional-resource:non-transactional-resource-all:jar:5.0.0.M9-SNAPSHOT: Could not find artifact org.wildfly:wildfly-arquillian-container-managed:jar:8.0.0.Beta1-SNAPSHOT -> [Help 1] [ERROR] {code} was:http://172.17.131.2/view/Narayana+BlackTie/job/narayana-quickstarts/35/consoleFull > TXFramework and XTS QS link to Beta1-SNAPSHOT of WildFly - needs to be Beta2 > ---------------------------------------------------------------------------- > > Key: JBTM-2011 > URL: https://issues.jboss.org/browse/JBTM-2011 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M9 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-quickstarts/35/co... > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 29.680s > [INFO] Finished at: Wed Nov 06 09:17:00 GMT 2013 > [INFO] Final Memory: 39M/94M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project non-transactional-resource-all: Could not resolve dependencies for project org.jboss.narayana.quickstart.xts.non-transactional-resource:non-transactional-resource-all:jar:5.0.0.M9-SNAPSHOT: Could not find artifact org.wildfly:wildfly-arquillian-container-managed:jar:8.0.0.Beta1-SNAPSHOT -> [Help 1] > [ERROR] > {code} -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2011) TXFramework and XTS QS link to Beta1-SNAPSHOT of WildFly - needs to be Beta2

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2011?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2011: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/107 > TXFramework and XTS QS link to Beta1-SNAPSHOT of WildFly - needs to be Beta2 > ---------------------------------------------------------------------------- > > Key: JBTM-2011 > URL: https://issues.jboss.org/browse/JBTM-2011 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M9 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-quickstarts/35/co... -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2011) TXFramework and XTS QS link to Beta1-SNAPSHOT of WildFly - needs to be Beta2

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2011: ----------------------------------- Summary: TXFramework and XTS QS link to Beta1-SNAPSHOT of WildFly - needs to be Beta2 Key: JBTM-2011 URL: https://issues.jboss.org/browse/JBTM-2011 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Demonstrator Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.M9 http://172.17.131.2/view/Narayana+BlackTie/job/narayana-quickstarts/35/co... -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2008) Quickstart: Running transactional queue quickstart hangs on linux

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2008?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2008: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Quickstart: Running transactional queue quickstart hangs on linux > ----------------------------------------------------------------- > > Key: JBTM-2008 > URL: https://issues.jboss.org/browse/JBTM-2008 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.M9 > > > From: http://172.17.131.2/job/narayana-quickstarts/26/console > BUILD SUCCESSFUL > [exec] Total time: 1 second > [exec] 2013-11-04 16:57:20,425 [0xb7789710] INFO (AtmiBrokerLogc :60 ) - Sent message 1 > [exec] 2013-11-04 16:57:20,482 [0xb7789710] INFO (AtmiBrokerLogc :60 ) - Sent message 2 > [exec] 2013-11-04 16:57:20,483 [0xb7789710] INFO (AtmiBrokerLogc :60 ) - Please press return after you: Press 1 to commit or 2 to rollback... > [exec] 2013-11-04 16:57:23,219 [0xb776a710] INFO (AtmiBrokerLogc :60 ) - Preparing to dequeue the messages: 2 > [exec] [33m16:59:24,443 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffffac118314:-6928ee76:52744556:95 in state RUN > [exec] [0m[33m16:59:24,444 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012095: Abort of action id 0:ffffac118314:-6928ee76:52744556:95 invoked while multiple threads active within it. > [exec] [0m[33m16:59:24,445 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012108: CheckedAction::check - atomic action 0:ffffac118314:-6928ee76:52744556:95 aborting with 1 threads active! > [exec] [0m[33m16:59:24,455 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffffac118314:-6928ee76:52744556:95 > Build timed out (after 20 minutes). Marking the build as failed. > [exec] [0m2013-11-04 17:04:51,503 [0xb776a710] INFO (AtmiBrokerClient :47 ) - SIGINT Detected: Shutting down client this may take several minutes > [exec] 2013-11-04 17:04:51,504 [0xb776a710] INFO (AtmiBrokerClient :49 ) - Shutdown complete > [exec] 2013-11-04 17:04:51,505 [0xb776a710] INFO (AtmiBrokerClient :47 ) - SIGINT Detected: Shutting down client this may take several minutes > [exec] 2013-11-04 17:04:51,505 [0xb776a710] INFO (AtmiBrokerClient :49 ) - Shutdown complete > Archiving artifacts > [exec] 2013-11-04 17:04:51,620 [0xb776a710] INFO (AtmiBrokerClient :47 ) - SIGINT Detected: Shutting down client this may take several minutes > [exec] 2013-11-04 17:04:51,621 [0xb776a710] INFO (AtmiBrokerClient :49 ) - Shutdown complete -- 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

10 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 November 2013