Webclient HTTP ERROR 404 / 503 after fresh build from source

[JuergeN]

HTTP ERROR 503

Problem accessing /de.deepamehta.webclient/index.html. Reason:

    java.lang.IllegalStateException: Can only add listeners while bundle is active or activating.

Caused by:

javax.servlet.UnavailableException: java.lang.IllegalStateException: Can only add listeners while bundle is active or activating.
	at org.mortbay.jetty.servlet.ServletHolder.makeUnavailable(ServletHolder.java:415)
	at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:458)
	at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
	at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:685)
	at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
	at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
	at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
	at org.mortbay.jetty.Server.doStart(Server.java:224)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
	at org.apache.felix.http.jetty.internal.JettyService.initializeJetty(JettyService.java:164)
	at org.apache.felix.http.jetty.internal.JettyService.startJetty(JettyService.java:115)
	at org.apache.felix.http.jetty.internal.JettyService.run(JettyService.java:290)
	at java.lang.Thread.run(Thread.java:636)

Powered by Jetty://

[JuergeN]

Troubleshooting:
If the browser shows 404 while this exception appears in the terminal ...

com.sun.jersey.api.container.ContainerException?: No WebApplication? provider is present

... then refresh the HTTP Jetty Bundle by typing "refresh 1" in the terminal (checkout the proper bundle ID before by using the "lb" command).

solves the problem for now.

[JuergeN]

This is a jetty / osgi / jersey issue. Other people are reporting similar problems. Needs further exploration. Known possible solutions:

1. working with osgi run levels
2. copy service manifests from jetty/jersey? to user application

[Jörg Richter]

Fix 404/503 after start (#17).

The error occured only in development environment (hot deployment via Felix File Install), that is when build from source. The solution is to have Jersey *before* Felix File Install in the bundle list. This is simply achieved by swapping the 2 provisions in the global POM:

<deployPoms>

deepamehta-provision/3rd-party-bundles/pom.xml,
deepamehta-provision/felix-bundles/pom.xml

</deployPoms>

Furthermore, setting <felix.fileinstall.noInitialDelay> back to false (the deafult) avoids a premature client start.

Close ticket 17.

• Changeset: 4391f3ef706a2ea2b72e34d36f5da436fa261dbe
• URL: ​https://github.com/jri/deepamehta/commit/4391f3ef706a2ea2b72e34d36f5da436fa261dbe