Shindig fails to start up properly when run with gadget support only (ie. with
-Druntype=gadgets)
-------------------------------------------------------------------------------------------------
Key: SHINDIG-1236
URL: https://issues.apache.org/jira/browse/SHINDIG-1236
Project: Shindig
Issue Type: Bug
Components: Java
Reporter: Bruce Godden
I updated my source tree in the late afternoon on Friday (UK time) to, I think,
revision 884712.
I built using: mvn -Dmaven.test.skip=true
I ran using: mvn jetty:run -Druntype=gadgets -Djetty.port=8080
The following error report was generated during start up:
WARN: Failed startup of context
org.mortbay.jetty.plugin.jetty6pluginwebappcont...@1a0283e{/,C:\bruce\shindig\wd2\java\server\target\shindig-server-1.1-BETA6-incubating-SNAPSHOT}
com.google.inject.CreationException: Guice creation errors:
1) No implementation for java.lang.Boolean annotated with
@com.google.inject.name.Named(value=shindig.allowUnauthenticated) was bound.
while locating java.lang.Boolean annotated with
@com.google.inject.name.Named(value=shindig.allowUnauthenticated)
for parameter 0 at
org.apache.shindig.auth.AnonymousAuthenticationHandler.<init>(AnonymousAuthenticationHandler.java:31)
while locating org.apache.shindig.auth.AnonymousAuthenticationHandler
for parameter 1 at
org.apache.shindig.gadgets.servlet.AuthenticationModule$AuthProvider.<init>(AuthenticationModule.java:50)
at
org.apache.shindig.gadgets.servlet.AuthenticationModule.configure(AuthenticationModule.java:42)
2) No implementation for java.lang.Long annotated with
@com.google.inject.name.Named(value=org.apache.shindig.serviceExp
irationDurationMinutes) was bound.
while locating java.lang.Long annotated with
@com.google.inject.name.Named(value=org.apache.shindig.serviceExpirationD
urationMinutes)
for parameter 1 at
org.apache.shindig.gadgets.render.DefaultRpcServiceLookup.<init>(DefaultRpcServiceLookup.java:57)
while locating org.apache.shindig.gadgets.render.RpcServiceLookup
for parameter 4 at
org.apache.shindig.gadgets.render.RenderingGadgetRewriter.<init>(RenderingGadgetRewriter.java:110
)
while locating org.apache.shindig.gadgets.render.RenderingGadgetRewriter
for parameter 6 at
org.apache.shindig.gadgets.rewrite.RewriteModule$GadgetRewritersProvider.<init>(RewriteModule.java:57)
at
org.apache.shindig.gadgets.rewrite.RewriteModule.configure(RewriteModule.java:42)
2 errors
at
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:354)
at
com.google.inject.InjectorBuilder.initializeStatically(InjectorBuilder.java:152)
at com.google.inject.InjectorBuilder.build(InjectorBuilder.java:105)
at com.google.inject.Guice.createInjector(Guice.java:92)
at
org.apache.shindig.common.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:64)
at
org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
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.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:441)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:383)
at
org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:210)
at
org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
When my gadget tried to access Shindig it got the error report:
HTTP ERROR: 503
Problem accessing /gadgets/ifr. Reason:
SERVICE_UNAVAILABLE
I tried the same thing with a previous version (circa BETA4) and exactly the
same thing happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
