It's all about the answers!

Ask a question

Run Jazz server in remote mode


Michele Pegoraro (1.8k14118103) | asked Jul 09 '09, 5:15 a.m.
Hi,
I'm trying to run jazz 2.0 server in remote mode using the following topic:
https://jazz.net/wiki/bin/view/Main/JazzServerRunAndDebug

I've created a new Java project, imported the launch configuration and tried to launch it. I've got no errors but the only thing I can see on console is

osgi>


and no one URL for jazz is accessible. What I'm doing wrong??

8 answers



permanent link
Todd Lainhart (40611) | answered Jul 09 '09, 9:42 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
I can't tell from the information that you've supplied here, but the server appears not to be running - if it was, you would see various server diagnostic output in the osgi console.

I would open your launch, and be sure that the jazz server plugins are selected as you expect.

Hi,
I'm trying to run jazz 2.0 server in remote mode using the following topic:
https://jazz.net/wiki/bin/view/Main/JazzServerRunAndDebug

I've created a new Java project, imported the launch configuration and tried to launch it. I've got no errors but the only thing I can see on console is

osgi>


and no one URL for jazz is accessible. What I'm doing wrong??

permanent link
Michele Pegoraro (1.8k14118103) | answered Jul 09 '09, 10:12 a.m.
Thank you for the answer. I have use the launch configuration for 2.0 provided by the page I've linked before. For that reason I was think that I missed something.
How do I do to know which plugins are part of server if the example launch does not work?

permanent link
Michele Pegoraro (1.8k14118103) | answered Jul 09 '09, 10:57 a.m.
Thank you for the answer. I have use the launch configuration for 2.0 provided by the page I've linked before. For that reason I was think that I missed something.
How do I do to know which plugins are part of server if the example launch does not work?

It seems that i was missing something: now I've set Jazz Server as Target Platform and the server is launched.
But it seems that it doesn't retry my DB information because I see only "Error fetching server status information" on admin web console.
If I try to put teamserver.properties url I got this error:

16:57:19,207 ERROR com.ibm.team.server.embedded.jetty.auth.Activator - Invalid URL specified for teamserver.properties
16:57:19,207 ERROR com.ibm.team.server.embedded.jetty.auth.Activator - Failed to locate teamserver.properties

but the address seems ok...

Without using teamserver.properties I got this error:
The "DERBY" database vendor is not supported by the server license.

permanent link
Michele Pegoraro (1.8k14118103) | answered Jul 09 '09, 11:29 a.m.
Using
https://jazz.net/wiki/bin/view/Main/DbVendorIsNotSupported
I've resolved my problem with DbVendor and now the server seems to run correctly.

I've always the problem if I want to specify teamserver.properties but it's secondary.

permanent link
josseph zhang (3612) | answered Jul 18 '09, 1:09 a.m.
Using
https://jazz.net/wiki/bin/view/Main/DbVendorIsNotSupported
I've resolved my problem with DbVendor and now the server seems to run correctly.

I've always the problem if I want to specify teamserver.properties but it's secondary.


Hi Michele,
I have set up rtc 2.0 development environment, and met the similar problem. I used RTC2.0 express-c version.


osgi> 12:39:47,562 [Start Level Event Dispatcher] ERROR com.ibm.team.server.embedded.jetty.auth.Activator - Failed to locate teamserver.properties
12:39:48.734 INFO [Start Level Event Dispatcher] org.mortbay.log.LogImpl.add(LogImpl.java:109) >21> added org.mortbay.log.OutputStreamLogSink@5a805a8
12:39:48.687 INFO [Start Level Event Dispatcher] org.mortbay.http.HttpServer.doStart(HttpServer.java:684) >16> Version Jetty/5.1.x
12:39:48.750 INFO [Start Level Event Dispatcher] org.mortbay.util.FileResource.<clinit>(FileResource.java:60) >24> Checking Resource aliases
12:39:51.921 INFO [Start Level Event Dispatcher] org.mortbay.util.Container.start(Container.java:75) >22> Started org.mortbay.jetty.servlet.WebApplicationHandler@1be01be
12:40:25.328 INFO [Start Level Event Dispatcher] org.mortbay.util.Container.start(Container.java:75) >17> Started WebApplicationContext[/jazz,/jazz]
12:40:25.375 INFO [Start Level Event Dispatcher] org.mortbay.http.SocketListener.start(SocketListener.java:205) >17> Started SocketListener on 0.0.0.0:9080
12:40:26.328 INFO [Start Level Event Dispatcher] org.mortbay.http.SocketListener.start(SocketListener.java:205) >17> Started SocketListener on 0.0.0.0:9443
12:40:26.328 INFO [Start Level Event Dispatcher] org.mortbay.util.Container.start(Container.java:75) >15> Started org.mortbay.jetty.Server@3a003a00
12:40:31,218 [SslListener1-4] INFO uration.OverridablePropertyFileServerConfiguration - CRJAZ1363I Loading configuration from "com.ibm.team.repository.common/teamserver.properties".
12:40:31,718 [SslListener1-4] WARN ory.service.AbstractConfigurationPropertyValidator - CRJAZ1236I A development time license is being used. If you are running an official build of the Jazz Team Server, then your license setup is in a bad state. Check the log for details about license installation failures.
12:40:31,750 [SslListener1-4] ERROR t.internal.registry.AbstractActivationManagerOwner - CRJAZ1093I Service failed to activate.
com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1126I The service "com.ibm.team.repository.service.internal.rdb.ConnectionPoolService" had some invalid configuration properties:
CRJAZ1125I The configuration property value "DERBY" is not valid for the property "db.vendor". The "DERBY" database vendor is not supported by the server license.

at com.ibm.team.repository.common.transport.internal.registry.ServiceConfiguration.getPropertiesMap(ServiceConfiguration.java:271)
at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.bindConfigurationProperties(AbstractActivationManagerOwner.java:189)
at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:542)
at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.activate(AbstractActivationManagerOwner.java:143)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.activate(BundleActivationManager.java:290)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.performActivation(BundleActivationManager.java:1584)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.access$2(BundleActivationManager.java:1569)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager$3.acquired(BundleActivationManager.java:573)
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.serviceAcquired(ImportServiceRecordContainer.java:587)
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.access$1(ImportServiceRecordContainer.java:571)
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer$5.serviceAcquired(ImportServiceRecordContainer.java:352)
at org.eclipse.soda.sat.core.internal.record.ImportServiceRecord.acquire(ImportServiceRecord.java:114)
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer$1.execute(ImportServiceRecordContainer.java:64)
at org.eclipse.soda.sat.core.internal.record.container.ServiceRecordContainer.doForService(ServiceRecordContainer.java:352)
at org.eclipse.soda.sat.core.internal.record.container.ServiceRecordContainer.doForEach(ServiceRecordContainer.java:319)
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.acquire(ImportServiceRecordContainer.java:303)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.acquireImportedServices(BundleActivationManager.java:234)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.acquireImportServiceRecords(BundleActivationManager.java:250)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.startSync(BundleActivationManager.java:2049)
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.start(BundleActivationManager.java:2018)
at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.register(OsgiServicesManager.java:404)
at com.ibm.team.repository.common.transport.services.TeamServiceRegistry.registerServices(TeamServiceRegistry.java:325)
at com.ibm.team.repository.common.transport.services.TeamServiceRegistry.initialize(TeamServiceRegistry.java:286)
at com.ibm.team.repository.common.transport.services.TeamServiceRegistry.start(TeamServiceRegistry.java:367)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.init(AbstractTeamServerServlet.java:1169)
at com.ibm.team.repository.servlet.TeamServerServlet.init(TeamServerServlet.java:195)
at javax.servlet.GenericServlet.init(GenericServlet.java:168)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.initializeDelegate(ServletManager.java:195)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:179)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)


It seems that you resolve it with DbVendor. Could you please tell me what steps to resolve it. The wiki page is a little old. https://jazz.net/wiki/bin/view/Main/DbVendorIsNotSupported
And if I want to do some extensions for rtc 2.0, could express-c be enough to do this?

Thanks in advance,
Joseph

permanent link
Michele Pegoraro (1.8k14118103) | answered Jul 18 '09, 3:29 a.m.
I resolved it as I said using the link.
Just take licence jar from /jazz/server/license-update-site/plugin and import on your project. Then you have to see this plugin from your launch configuration. If you does not see it, change your target platform (from Preferences->Plug-in Development->Target Platform) adding the license plugin, and then add it in your launch configuration.

permanent link
josseph zhang (3612) | answered Jul 18 '09, 6:09 a.m.
I resolved it as I said using the link.
Just take licence jar from /jazz/server/license-update-site/plugin and import on your project. Then you have to see this plugin from your launch configuration. If you does not see it, change your target platform (from Preferences->Plug-in Development->Target Platform) adding the license plugin, and then add it in your launch configuration.


Great. I resolved it with your solution. Thanks a lot for your quick response.

Regards,
Joseph

permanent link
enzo zuk (12693) | answered Jul 23 '09, 1:01 p.m.
this solution is ok, jazz server run...
but seems to be a problem looking the server status from the rtc console:

osgi> 18:50:43,410 ERROR com.ibm.team.server.embedded.jetty.auth.Activator - Failed to locate teamserver.properties
18:50:43.660 INFO org.mortbay.log.LogImpl.add(LogImpl.java:109) >21> added org.mortbay.log.OutputStreamLogSink@200a200a
18:50:43.426 INFO org.mortbay.http.HttpServer.doStart(HttpServer.java:684) >16> Version Jetty/5.1.x
18:50:43.676 INFO org.mortbay.util.FileResource.<clinit>(FileResource.java:60) >24> Checking Resource aliases
18:50:47.154 INFO org.mortbay.util.Container.start(Container.java:75) >22> Started org.mortbay.jetty.servlet.WebApplicationHandler@579a579a
18:51:49.508 INFO org.mortbay.util.Container.start(Container.java:75) >17> Started WebApplicationContext
18:51:49.554 INFO org.mortbay.http.SocketListener.start(SocketListener.java:205) >17> Started SocketListener on 0.0.0.0:9080
18:51:50.865 INFO org.mortbay.http.SocketListener.start(SocketListener.java:205) >17> Started SocketListener on 0.0.0.0:9443
18:51:50.880 INFO org.mortbay.util.Container.start(Container.java:75) >15> Started org.mortbay.jetty.Server@6d726d72

Your answer


Register or 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.