Announcement Announcement Module
Collapse
No announcement yet.
com.springsource.server.repository bundle fails to start Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • com.springsource.server.repository bundle fails to start

    Hi,

    We're in the process of upgrading from DM Server 2.0.0.M2 to M3, and although everything that we've deployed appears to be working fine, the following error appears on startup

    <SPWE0005E> Failed to start web bundle '/com.springsource.server.repository': consult the Server trace.log for further details
    The trace log shows the following:

    Code:
    [2009-08-04 10:23:00.005] Thread-19                .springsource.server.web.core.internal.WebApplicationEventLogger E <SPWE0005E> Failed to start web bundle '/com.springsource.server.repository': consult the Server trace.log for further details.
    [2009-08-04 10:26:55.410] async-delivery-thread-1             org.springframework.web.context.ContextLoader.unknown E Context initialization failed
    org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from ServletContext resource [/WEB-INF/applicationContext.xml]; nested exception is java.io.FileNotFoundException: Could not open ServletContext resource [/WEB-INF/applicationContext.xml]
            at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:323)
            at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:284)
            at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
            at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
            at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
            at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:125)
            at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:93)
            at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:127)
            at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:425)
            at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:355)
            at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
            at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:198)
            at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
            at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
            at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
            at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
            at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
            at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
            at com.springsource.osgi.webcontainer.tomcat.TomcatServletContainer.startWebApplication(TomcatServletContainer.java:117)
            at com.springsource.osgi.webcontainer.internal.StandardWebContainer$StandardWebApplication.start(StandardWebContainer.java:102)
            at com.springsource.server.web.core.internal.WebBundlePersonality.onStarted(WebBundlePersonality.java:84)
            at com.springsource.kernel.deployer.core.module.AbstractModule.onStarted(AbstractModule.java:218)
            at com.springsource.kernel.deployer.core.module.StandardModule.onStarted(StandardModule.java:654)
            at com.springsource.kernel.deployer.core.module.DeployerBundleListener$2$1.run(DeployerBundleListener.java:148)
            at com.springsource.kernel.concurrent.ExecutorServiceDelegate$KernelRunnable.run(ExecutorServiceDelegate.java:121)
            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
            at java.lang.Thread.run(Thread.java:619)
    Caused by: java.io.FileNotFoundException: Could not open ServletContext resource [/WEB-INF/applicationContext.xml]
            at org.springframework.web.context.support.ServletContextResource.getInputStream(ServletContextResource.java:118)
            at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
            ... 27 more
    If I have a look in what's been deployed for the bundle in question in the 'work'-directory, there is, as the error suggests, no WEB-INF/applicationContext.xml present.

    The server is a 64-bit Linux-machine running a 64-bit JVM:
    java version "1.6.0_13"
    Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
    Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02, mixed mode)
    Running the same configuration on a 32-bit Windows desktop works fine, and nothing similar can be seen when starting the M2-version. Is this a known issue? Is it likely to be a configuration error?

    Thanks!
    Tom

  • #2
    Thanks, Tom. This problem was caused by a capitalisation issue with the application context file. The file was named ApplicationContext.xml, but Spring was expecting to find a file named applicationContext.xml. It worked fine on both Mac and Windows as their filesystems are case-insensitive. It breaks on Linux due to its case-sensitive filesystem.

    The good news is that this problem has been fixed in the latest nightly builds. We've also added Linux to the platforms on which we run CI so that we'll catch this sort of problem earlier in the future.

    If you'd prefer not to move up to a nightly build, we should be releasing M4 in the next couple of days.

    Comment


    • #3
      Ok, great. I think I'll hold off until M4 is released. Is there an overall roadmap for DM Server 2.0.0 available online somewhere? I'd be very interested in where you are now in relation to the final release.

      Thanks
      Tom

      Comment

      Working...
      X