Problems with Jazztalk JUnit launch
Hello,
I am having trouble getting the JUnit launch to work with the JazzTalk example.
The first test (com.ibm.team.repository.service.tests.TestDbRebuild > testRebuildAlll) works fine, but the second (com.ibm.team.repository.service.tests.TestDbInit > testRepositoryInited) fails.
The console errors I am getting are as follows, followed by a number of more address already in use errors. Am I missing a step that I need to do before I run the junit test?
Thanks,
Jamie
12:48:42,109 ERROR com.ibm.team.server.embedded.jetty.auth.Activator - Failed to locate teamserver.properties
12:48:43,062 WARN org.mortbay.util.ThreadedServer - Failed to start: SocketListener0@0.0.0.0:9080
12:48:44,343 WARN org.mortbay.util.ThreadedServer - Failed to start: SslListener1@0.0.0.0:9443
org.mortbay.util.MultiException
I am having trouble getting the JUnit launch to work with the JazzTalk example.
The first test (com.ibm.team.repository.service.tests.TestDbRebuild > testRebuildAlll) works fine, but the second (com.ibm.team.repository.service.tests.TestDbInit > testRepositoryInited) fails.
The console errors I am getting are as follows, followed by a number of more address already in use errors. Am I missing a step that I need to do before I run the junit test?
Thanks,
Jamie
12:48:42,109 ERROR com.ibm.team.server.embedded.jetty.auth.Activator - Failed to locate teamserver.properties
12:48:43,062 WARN org.mortbay.util.ThreadedServer - Failed to start: SocketListener0@0.0.0.0:9080
12:48:44,343 WARN org.mortbay.util.ThreadedServer - Failed to start: SslListener1@0.0.0.0:9443
org.mortbay.util.MultiException
12 answers
Could this happen because I am using those ports for my copy of Jazz that I am developing with? It didn't look like there were any other instances of the server running. Do I need to point my launch directives to a jdbc location that has anything specific in it already (like a team.properties file?)
Thanks,
Jamie
Thanks,
Jamie
jsamdal wrote:
The first test wants to lock the database, so it would fail if another
program was connected to the database.
The second test wants to lock the database *and* lock the network ports
indicated (9080 and 9443). The fact that this test is failing suggests
that there is another program using those ports - probably another
instance of Jetty.
This might happen if you were running another example that used a
different database instance (like HiJazz or JazzBot) and left that
instance of the Jazz server running.
Look in the Console view and find the button with the dropdown menu that
has the tooltip "Display Selected Console". You can use that dropdown
to switch consoles. You may see multiple consoles there where some are
labeled with a <terminated> prefix and others are not. The latter
represent programs that are still running. You can use the "Terminate"
button (big red square icon) to stop those programs from running.
So basically I would poke around to figure out what's running (probably
some instance of Jetty) and stop it and then try running the database
creation test again.
Chris
Hello,
I am having trouble getting the JUnit launch to work with the JazzTalk
example.
The first test (com.ibm.team.repository.service.tests.TestDbRebuild
testRebuildAlll) works fine, but the second
(com.ibm.team.repository.service.tests.TestDbInit
testRepositoryInited) fails.
The first test wants to lock the database, so it would fail if another
program was connected to the database.
The second test wants to lock the database *and* lock the network ports
indicated (9080 and 9443). The fact that this test is failing suggests
that there is another program using those ports - probably another
instance of Jetty.
This might happen if you were running another example that used a
different database instance (like HiJazz or JazzBot) and left that
instance of the Jazz server running.
Look in the Console view and find the button with the dropdown menu that
has the tooltip "Display Selected Console". You can use that dropdown
to switch consoles. You may see multiple consoles there where some are
labeled with a <terminated> prefix and others are not. The latter
represent programs that are still running. You can use the "Terminate"
button (big red square icon) to stop those programs from running.
So basically I would poke around to figure out what's running (probably
some instance of Jetty) and stop it and then try running the database
creation test again.
Chris
page 2of 1 pagesof 2 pages