[
https://issues.apache.org/jira/browse/ACE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503033#comment-13503033
]
Tuomas Kiviaho commented on ACE-305:
------------------------------------
I started up the devserver with run.sh command and this is what I got in
console. UI gave me 503 and this error each time I tried to access it. By
manually turning off webui, vaadin and felix http and starting them in reverse
order got e around this issue. Usage of startlevel in run.sh ensured that the
Felix Http got started before the others and I totally agree that it's just a
workaround and not an ideal solution. I have no idea how felix http internals
work but the problem seems to have risen elsewhere as well
https://github.com/bndtools/bndtools/issues/28 (not a bug in jetty as mentioned
but has something to do with how felix http hooks to it). I'm getting three
time the message of vaadin starting up to console when I shutdown and start the
system again. Alternative - although a bit biased - workaround could be to
switch over to Pax Web where timing issues have been dealt with in the latest
major version since both implement what is referred as Web Experience
<http://wiki.osgi.org/wiki/WebExperience> that ACE seems to be using.
> Start level problems with devserver
> -----------------------------------
>
> Key: ACE-305
> URL: https://issues.apache.org/jira/browse/ACE-305
> Project: ACE
> Issue Type: Bug
> Reporter: Tuomas Kiviaho
>
> Pax runner script gives followind exception in certain cases. This is easily
> avoided by lowering start level for required bundles.
> java.lang.IllegalStateException: Can only register services while bundle is
> active or activating.
> at org.apache.felix.framework.Felix.registerService(Felix.java:3209)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
> at
> org.apache.felix.http.base.internal.HttpServiceController.register(HttpServiceController.java:135)
> at
> org.apache.felix.http.base.internal.DispatcherServlet.init(DispatcherServlet.java:48)
> at
> org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:440)
> 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:662)
> [INFO] Started jetty 6.1.x at port(s) HTTP:8082
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
