November 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1683: ------------------------------------- I think we should just add: taskkill /F /IM java.exe For some reason the java.exe that Jenkins runs under is not in the tasklist so it is safe to do it (I just did myself :) ) http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/killjava... > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1683: ------------------------------------- I think the problem is that narayana.bat does not kill the java app server process. We should try to augment narayana.bat to kill it: https://github.com/jbosstm/narayana/blob/master/scripts/hudson/narayana.b... We do try to call shutdown.bat but if that hangs we don't have a mechanism to kill the process at the operating system level. We can test it out by creating a new job to target the killing because we don't have rdesktop to the node at the moment anyway so we need this right now :) > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl?

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2299?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2299: ------------------------------------- That sounds right, it looks like a relic and should be pruned. > Why does Blacktie have its own CosTransactions.idl? > --------------------------------------------------- > > Key: JBTM-2299 > URL: https://issues.jboss.org/browse/JBTM-2299 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Amos Feng > > Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl?

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2299?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2299: --------------------------------- It looks like we don't need it as we has removed the TAO dependency in JBTM-1665 and used the http rest methods to access the TM [~tomjenkinson], Does it make sense ? > Why does Blacktie have its own CosTransactions.idl? > --------------------------------------------------- > > Key: JBTM-2299 > URL: https://issues.jboss.org/browse/JBTM-2299 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Amos Feng > > Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2297) Store docker image for service(s) in JBoss repo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2297?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2297: -------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > Store docker image for service(s) in JBoss repo > ----------------------------------------------- > > Key: JBTM-2297 > URL: https://issues.jboss.org/browse/JBTM-2297 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > > We have a repo for JBoss project docker images. Store our final version (not POC version I created) there. Also see if this also suggests a way of distributing and storing the docker file to create it/them. I'm assuming we don't need to store this information within the Narayana repo, but perhaps we do and in which case we'll probably need a docker directory. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2298) Use Project Atomic for docker image(s)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2298: -------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > Use Project Atomic for docker image(s) > -------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > > When I created the initial docker (POC) image I did so using a standard Fedora base image. We should also look at supporting the Project Atomic docker image, since it's important for Red Hat. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2295: -------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2296: -------------------------------- Assignee: Gytis Trikleris (was: Tom Jenkinson) > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1683: --------------------------------- I'm thinking to disable the btadmin tests on the windows temporarily and create the other CI job to run. > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2300) XATMI implemenation tests failed

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2300: --------------------------------- {code} 2014-11-19 21:38:59,659 [0x4ed7d40] DEBUG (HybridConnectionImpl :164 ) - Response: ERROR, javax.jms.JMSException: Failed to create session factory at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:673) at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:112) at org.codehaus.stomp.jms.ProtocolConverter.onStompConnect(ProtocolConverter.java:229) at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:182) at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) at java.lang.Thread.run(Thread.java:744) Caused by: HornetQNotConnectedException[errorType=NOT_CONNECTED message=HQ119007: Cannot connect to server(s). Tried with all available servers.] at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:901) at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:669) ... 5 more {code} It looks like the hornetq error and need more investigating. > XATMI implemenation tests failed > -------------------------------- > > Key: JBTM-2300 > URL: https://issues.jboss.org/browse/JBTM-2300 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/694/PROFIL... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 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 2014