Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Problem during db Init

Hi,

When I try to launch the db Initializer I get an error in the testRebuildAll
step. The Unit tests terminates after this error and I see the following
trace in the console window. I have tried deleting the c:\testDb folder and
also tried cleaning up the junit workspace without any luck.

!ENTRY org.eclipse.equinox.app 4 0 2008-01-02 12:58:16.229

!MESSAGE Error in invoking method.

!STACK 0

java.lang.RuntimeException: No Server Container Descriptors were found on
the classpath. Please check that the Jetty bundles are included in your
launch or packaging.

at
com.ibm.team.repository.transport.client.TeamServerFactoryImpl.startLocalServer(TeamServerFactoryImpl.java:144)

at
com.ibm.team.repository.transport.client.TeamServerFactoryImpl.newTeamServerFromURL(TeamServerFactoryImpl.java:168)

at
com.ibm.team.repository.transport.client.TeamServerFactory.newTeamServerFromURL(TeamServerFactory.java:90)

at
com.ibm.team.repository.service.tests.remotetests.ServiceTestClientHelper.getTeamServer(ServiceTestClientHelper.java:80)

at
com.ibm.team.repository.service.tests.remotetests.ServiceTestClientHelper.getService(ServiceTestClientHelper.java:73)

at
com.ibm.team.repository.service.tests.remotetests.ServiceTestClientHelper.getService(ServiceTestClientHelper.java:64)

at
com.ibm.team.repository.service.tests.remotetests.RemoteServiceTestCaseHelper.run(RemoteServiceTestCaseHelper.java:92)

at
com.ibm.team.repository.service.tests.AbstractRemoteServiceTestCase.run(AbstractRemoteServiceTestCase.java:90)

at junit.framework.TestSuite.runTest(TestSuite.java:230)

at junit.framework.TestSuite.run(TestSuite.java:225)

at junit.framework.TestSuite.runTest(TestSuite.java:230)

at junit.framework.TestSuite.run(TestSuite.java:225)

at junit.framework.TestSuite.runTest(TestSuite.java:230)

at junit.framework.TestSuite.run(TestSuite.java:225)

at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)

at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)

at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)

at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)

at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)

at
org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:58)

at
org.eclipse.pde.internal.junit.runtime.CoreTestApplication.run(CoreTestApplication.java:24)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:615)

at
org.eclipse.equinox.internal.app.EclipseAppContainer.callMethod(EclipseAppContainer.java:572)

at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:171)

at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)

at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:615)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)

at org.eclipse.equinox.launcher.Main.run(Main.java:1173)

at org.eclipse.equinox.launcher.Main.main(Main.java:1148)



Thansk and Regards,

Praveen

0 votes



One answer

Permanent link
Praveen Sinha wrote:
Hi,

When I try to launch the db Initializer I get an error in the testRebuildAll
step. The Unit tests terminates after this error and I see the following
trace in the console window. I have tried deleting the c:\testDb folder and
also tried cleaning up the junit workspace without any luck.

!ENTRY org.eclipse.equinox.app 4 0 2008-01-02 12:58:16.229

!MESSAGE Error in invoking method.

!STACK 0

java.lang.RuntimeException: No Server Container Descriptors were found on
the classpath. Please check that the Jetty bundles are included in your
launch or packaging.

at
com.ibm.team.repository.transport.client.TeamServerFactoryImpl.startLocalServer(TeamServerFactoryImpl.java:144)
...

Hi Praveen,

I see TeamServerFactoryImpl is using ServerContainerProviderRegistry
which looks at extenders of
com.ibm.team.repository.common.serverContainerProviders. The only
plugin I see extending that extension-point is:

com.ibm.team.server.embedded.jetty.auth

So I'm guessing that plugin is missing from your launch config. Can you
try adding it?


Chris

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 10,938

Question asked: Jan 02 '08, 4:08 a.m.

Question was seen: 7,974 times

Last updated: Jan 02 '08, 4:08 a.m.

Confirmation Cancel Confirm