pongasoft / glu

Deployment Automation Platform
Apache License 2.0
518 stars 99 forks source link

Problem starting Jetty #252

Closed ypujante closed 10 years ago

ypujante commented 10 years ago

See forum thread: http://glu.977617.n3.nabble.com/Problem-starting-Jetty-td4026244.html

2013-11-01 18:01:54.402:WARN:oejw.WebAppContext:Failed startup of context o.e.j.w.WebAppContext{/console,file:/opt/glu/console-server/glu/repository/exploded-wars/org.linkedin.glu.console-webapp-5.3.1/},/opt/glu/console-server/glu/repository/exploded-wars/org.linkedin.glu.console-webapp-5.3.1 
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.linkedin.glu.orchestration.engine.delta.UserCustomDeltaDefinitionValidator': Cannot resolve reference to bean 'org.linkedin.glu.orchestration.engine.delta.UserCustomDeltaDefinitionDomainClass' while setting bean property 'domainClass'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'org.linkedin.glu.orchestration.engine.delta.UserCustomDeltaDefinitionDomainClass' is defined 
        at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:775) 
        at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:424) 
        at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:767) 

Caused by: 
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'org.linkedin.glu.orchestration.engine.delta.UserCustomDeltaDefinitionDomainClass' is defined 
        at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:775) 
        at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:424) 
        at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:767) 
        at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:249) 
ypujante commented 10 years ago

"Fixed" in glu 5.4.0. Added debug capability in case it happens again. I believe it is a plugin order issue...