Launching the server from Eclipse 3.4 not working
Does anyone have a working lauch configuration for running the Jazz
server M6a from Eclipse 3.4? I took the launch configuration from the wiki, hacked it, and it's not working. Any idea why the container starts, then immediately stops? osgi> log4j:WARN No appenders could be found for logger (com.ibm.team.repository.jndi.internal.Activator). log4j:WARN Please initialize the log4j system properly. 12:42:51.442 INFO org.mortbay.log.LogImpl.add(LogImpl.java:109) >21> added org.mortbay.log.OutputStreamLogSink@447c32 12:42:51.420 INFO org.mortbay.http.HttpServer.doStart(HttpServer.java:684) >16> Version Jetty/5.1.x 12:42:51.452 INFO org.mortbay.util.FileResource.<clinit>(FileResource.java:60) >22> Checking Resource aliases 12:42:51.921 INFO org.mortbay.util.Container.start(Container.java:75) >22> Started org.mortbay.jetty.servlet.WebApplicationHandler@1fa06 12:42:51.936 INFO org.mortbay.util.Container.start(Container.java:75) >17> Started WebApplicationContext 12:42:51.943 INFO org.mortbay.http.SocketListener.start(SocketListener.java:205) >17> Started SocketListener on 0.0.0.0:9080 12:42:52.428 INFO org.mortbay.http.SocketListener.start(SocketListener.java:205) >17> Started SocketListener on 0.0.0.0:9443 12:42:52.428 INFO org.mortbay.util.Container.start(Container.java:75) >15> Started org.mortbay.jetty.Server@fd357f 12:43:03.548 INFO ] org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:659) 01> Stopping Acceptor 12:43:03.649 INFO org.mortbay.http.SocketListener.stop(SocketListener.java:213) >27> Stopped SocketListener on 0.0.0.0:9080 12:43:03.651 INFO ]] org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:659) 01> Stopping Acceptor ] 12:43:03.752 INFO org.mortbay.http.SocketListener.stop(SocketListener.java:213) >27> Stopped SocketListener on 0.0.0.0:9443 12:43:03.764 INFO org.mortbay.util.Container.stop(Container.java:166) >32> Stopped org.mortbay.jetty.servlet.WebApplicationHandler@1fa06 12:43:03.764 INFO org.mortbay.util.Container.stop(Container.java:166) >28> Stopped WebApplicationContext 12:43:03.764 INFO org.mortbay.util.Container.stop(Container.java:166) >25> Stopped org.mortbay.jetty.Server@fd357f 2008-05-12 12:43:03.771 - FrameworkManager: (SAT-110.1101) A framework error has occurred. java.lang.NullPointerException at net.jazz.ajax.internal.Activator.removedService(Activator.java:81) at org.osgi.util.tracker.ServiceTracker$Tracked.untrack(ServiceTracker.java:1160) at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:991) at org.eclipse.osgi.framework.internal.core.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:91) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:1248) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:141) at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEventPrivileged(Framework.java:1563) at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEvent(Framework.java:1538) at org.eclipse.osgi.framework.internal.core.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:177) at org.eclipse.equinox.http.servlet.internal.Activator.removeProxyServlet(Activator.java:84) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.destroy(ProxyServlet.java:43) at org.mortbay.jetty.servlet.ServletHolder.stop(ServletHolder.java:270) at org.mortbay.jetty.servlet.ServletHandler.doStop(ServletHandler.java:469) at org.mortbay.jetty.servlet.WebApplicationHandler.doStop(WebApplicationHandler.java:354) at org.mortbay.util.Container.stop(Container.java:163) at org.mortbay.http.HttpContext.doStop(HttpContext.java:1760) at org.mortbay.jetty.servlet.ServletHttpContext.doStop(ServletHttpContext.java:231) at org.mortbay.jetty.servlet.WebApplicationContext.doStop(WebApplicationContext.java:572) at org.mortbay.util.Container.stop(Container.java:163) at org.mortbay.http.HttpContext.stop(HttpContext.java:1728) at org.mortbay.http.HttpServer.doStop(HttpServer.java:751) at org.mortbay.util.Container.stop(Container.java:163) at com.ibm.team.server.embedded.jetty.Activator.stop(Activator.java:175) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$3.run(BundleContextImpl.java:1050) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:1046) at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:457) at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:531) at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1104) at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:655) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:312) at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:257) at org.eclipse.osgi.framework.internal.core.SystemBundle.suspend(SystemBundle.java:236) at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:678) at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:576) at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.java:41) at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:417) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:200) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) |
2 answers
Jetty launches will auto-shutdown in 3.4, you have to add the osgi.noShutdown=true property to tell the framework to keep running even if there are no applications found.
|
That did the trick. Thanks.
On 2008-05-12 19:07:54 -0500, Jean-Michel_Lemieux@ca.ibm-dot-com.no-spam.invalid (jlemieux) said: Jetty launches will auto-shutdown in 3.4, you have to add the |
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.