Announcement Announcement Module
Collapse
No announcement yet.
Try refreshing the springsource.server.web.dm_2 bundle Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Try refreshing the springsource.server.web.dm_2 bundle

    Hi,


    I'm trying out dm server 2 with an application designed for dm server 1.
    It's a very simple application, not sure if I'm encountering a bug in dm server 2 or I am missing a new configuration value.
    Tried it on both dm server 2 M2 and the latest snapshot springsource-dm-server-2.0.0.CI-R257-B210. Keep getting : "No dependent constraint mismatch - Try refreshing the <PAR_NAME-com.springsource.server.web.dm_2.0.0.D-71> bundle"

    Code:
    Unable to install application from location 'file:/springsource-dm-server-2.0.0.CI-R257-B210/work/com.springsource.kernel/upload/dmserver.vehicle-old-1.0.0.par'. Could not satisfy constraints for bundle 'dmserver.vehicle-1-dmserver.vehicle.web' at version '1.0.0'. Cannot resolve: dmserver.vehicle-1-dmserver.vehicle.web
        Resolver report:
            Uses violation: <Import-Package: com.springsource.server.web.dm; version="0.0.0"> in bundle <dmserver.vehicle-1-dmserver.vehicle.web_1.0.0>
                Possible matches:
                    	<Export-Package: com.springsource.server.web.dm; version="1.0.0"> from <dmserver.vehicle-1-com.springsource.server.web.dm_2.0.0.D-71>
                        No dependent constraint mismatch. Try refreshing the <dmserver.vehicle-1-com.springsource.server.web.dm_2.0.0.D-71> bundle.
    .
    [2009-05-25 09:07:58.486] server-tomcat-thread-4   <SPDE0011E> Deployment of 'dmserver.vehicle' version '1' failed.
    Any ideas if this is a new configuration parameter I'm missing ? Or could this be a bug ?

  • #2
    My guess would be that this is a bug, most likely in the cloning support that's been added to dm Server 2.0.

    Does your dm Server 1.0 application depend upon Spring 2.5.6? If so, then it'll be using auto-cloning to accommodate the two different versions of Spring. The console output generated during deployment should show what's happening. Could you post it, please?

    Comment


    • #3
      Thanks for you reply Andy.

      As a matter of fact, a 'cloning' message does appears right before the error, here is the stack:

      Code:
      [2009-05-26 10:47:16.021] async-delivery-thread-1  <SPSC1001I> Starting web application '/'.
      [2009-05-26 10:47:31.491] fs-watcher               <SPDE0048I> Processing 'CREATED' event for file 'dmserver.vehicle-1.0.0.par'.
      [2009-05-26 10:47:54.973] fs-watcher               <SPDE0053I> Cloned bundles: org.springframework.jdbc_2.5.5.A, org.springframework.web_2.5.5.A, com.springsource.server.web.dm_2.0.0.D-71, org.springframework.web.servlet_2.5.5.A, com.springsource.org.apache.derby.client_10.4.1000003.648739, org.springframework.aspects_2.5.5.A, org.springframework.transaction_2.5.5.A, org.springframework.orm_2.5.5.A, org.springframework.context.support_2.5.5.A, org.springframework.jms_2.5.5.A, org.springframework.context_2.5.5.A, org.springframework.aop_2.5.5.A, com.springsource.org.apache.commons.dbcp_1.2.2.osgi, org.springframework.beans_2.5.5.A.
      [2009-05-26 10:48:03.279] fs-watcher               <SPFF0000I> Wrote dump files into "/springdmserver/springsource-dm-server-2.0.0.CI-R257-B210/serviceability/dump/20090526104802-0"
      [2009-05-26 10:48:03.856] fs-watcher               <SPDE0018E> Unable to install application from location 'file:/springdmserver/springsource-dm-server-2.0.0.CI-R257-B210/pickup/dmserver.vehicle-1.0.0.par'. Could not satisfy constraints for bundle 'dmserver.vehicle-1-dmserver.vehicle.web' at version '1.0.0'. Cannot resolve: dmserver.vehicle-1-dmserver.vehicle.web
          Resolver report:
              Uses violation: <Import-Package: com.springsource.server.web.dm; version="0.0.0"> in bundle <dmserver.vehicle-1-dmserver.vehicle.web_1.0.0>
                  Possible matches:
                              <Export-Package: com.springsource.server.web.dm; version="1.0.0"> from <dmserver.vehicle-1-com.springsource.server.web.dm_2.0.0.D-71>
                          No dependent constraint mismatch. Try refreshing the <dmserver.vehicle-1-com.springsource.server.web.dm_2.0.0.D-71> bundle.
      .
      [2009-05-26 10:48:03.858] fs-watcher               <SPDE0011E> Deployment of 'dmserver.vehicle' version '1' failed.
      [2009-05-26 10:48:03.865] fs-watcher               <SPDE0005E> Hot deploy failed for resource '/springdmserver/springsource-dm-server-2.0.0.CI-R257-B210/pickup/dmserver.vehicle-1.0.0.par'.

      Comment


      • #4
        Thanks for the info.

        Ok, so this would appear to be a bug in 2.0's cloning support. Can you please open a JIRA? It'd be great if you could attach your application to the JIRA, or if it's too big, or it contains private content, the manifest for each bundle in the application should be sufficient.

        As a workaround while we're investigating the problem, you may like to try updating your application to use Spring 3.0. This will remove the need for it to use cloning.

        Comment


        • #5
          Opened a JIRA - https://issuetracker.springsource.com/browse/DMS-779

          I upgraded to Spring 3.0, but now I'm getting what appears to be a Spring 3.0 related error.

          Code:
          java.lang.RuntimeException: java.io.FileNotFoundException: class path resource [org/springframework/orm/jpa/LocalContainerEntityManagerFactoryBean.class] cannot be opened because it does not exist
          	at org.springframework.context.annotation.ConfigurationClassPostProcessor.isConfigurationClassBeanDefinition(ConfigurationClassPostProcessor.java:208)
          	at org.springframework.context.annotation.ConfigurationClassPostProcessor.getConfigurationBeanDefinitions(ConfigurationClassPostProcessor.java:127)
          	at org.springframework.context.annotation.AbstractConfigurationClassProcessor.processConfigBeanDefinitions(AbstractConfigurationClassProcessor.java:98)
          	at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanFactory(ConfigurationClassPostProcessor.java:95)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.invokeBeanFactoryPostProcessors(AbstractDelegatedExecutionApplicationContext.java:479)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.invokeBeanFactoryPostProcessors(AbstractDelegatedExecutionApplicationContext.java:459)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.invokeBeanFactoryPostProcessors(AbstractDelegatedExecutionApplicationContext.java:395)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$3.run(AbstractDelegatedExecutionApplicationContext.java:281)
          	at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.startRefresh(AbstractDelegatedExecutionApplicationContext.java:247)
          	at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.stageOne(DependencyWaiterApplicationContextExecutor.java:222)
          	at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.refresh(DependencyWaiterApplicationContextExecutor.java:175)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:175)
          	at org.springframework.osgi.extender.internal.activator.ContextLoaderListener$2.run(ContextLoaderListener.java:718)
          	at com.springsource.kernel.dmfragment.internal.ContextPropagatingTaskExecutor$2.run(ContextPropagatingTaskExecutor.java:82)
          	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: class path resource [org/springframework/orm/jpa/LocalContainerEntityManagerFactoryBean.class] cannot be opened because it does not exist
          	at org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:143)
          	at org.springframework.core.type.classreading.SimpleMetadataReaderFactory.getMetadataReader(SimpleMetadataReaderFactory.java:73)
          	at org.springframework.core.type.classreading.SimpleMetadataReaderFactory.getMetadataReader(SimpleMetadataReaderFactory.java:69)
          	at org.springframework.context.annotation.ConfigurationClassPostProcessor.isConfigurationClassBeanDefinition(ConfigurationClassPostProcessor.java:199)
          	... 17 more
          
          [2009-05-27 12:45:37.664] server-dm-4              <SPDE0020E> Application context creation failure for bundle 'com.apress.prodmserver.vehicle-1-com.apress.prodmserver.vehicle.repository.jpa-1.0.0.jar'.
          java.lang.RuntimeException: java.io.FileNotFoundException: class path resource [org/springframework/orm/jpa/LocalContainerEntityManagerFactoryBean.class] cannot be opened because it does not exist
          	at org.springframework.context.annotation.ConfigurationClassPostProcessor.isConfigurationClassBeanDefinition(ConfigurationClassPostProcessor.java:208)
          	at org.springframework.context.annotation.ConfigurationClassPostProcessor.getConfigurationBeanDefinitions(ConfigurationClassPostProcessor.java:127)
          	at org.springframework.context.annotation.AbstractConfigurationClassProcessor.processConfigBeanDefinitions(AbstractConfigurationClassProcessor.java:98)
          	at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanFactory(ConfigurationClassPostProcessor.java:95)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.invokeBeanFactoryPostProcessors(AbstractDelegatedExecutionApplicationContext.java:479)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.invokeBeanFactoryPostProcessors(AbstractDelegatedExecutionApplicationContext.java:459)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.invokeBeanFactoryPostProcessors(AbstractDelegatedExecutionApplicationContext.java:395)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$3.run(AbstractDelegatedExecutionApplicationContext.java:281)
          	at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.startRefresh(AbstractDelegatedExecutionApplicationContext.java:247)
          	at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.stageOne(DependencyWaiterApplicationContextExecutor.java:222)
          	at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.refresh(DependencyWaiterApplicationContextExecutor.java:175)
          	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:175)
          	at org.springframework.osgi.extender.internal.activator.ContextLoaderListener$2.run(ContextLoaderListener.java:718)
          	at com.springsource.kernel.dmfragment.internal.ContextPropagatingTaskExecutor$2.run(ContextPropagatingTaskExecutor.java:82)
          	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: class path resource [org/springframework/orm/jpa/LocalContainerEntityManagerFactoryBean.class] cannot be opened because it does not exist
          	at org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:143)
          	at org.springframework.core.type.classreading.SimpleMetadataReaderFactory.getMetadataReader(SimpleMetadataReaderFactory.java:73)
          	at org.springframework.core.type.classreading.SimpleMetadataReaderFactory.getMetadataReader(SimpleMetadataReaderFactory.java:69)
          	at org.springframework.context.annotation.ConfigurationClassPostProcessor.isConfigurationClassBeanDefinition(ConfigurationClassPostProcessor.java:199)
          	... 17 more
          Any idea if this particular package/class ceased to exist or changed name from 2.5 to 3.0? Or perhaps just a missing dependency (Export) in the 3.0.0.CI-217 milestone release used by the dm Server ?
          I guess I could post to the general Spring 3.0 section, but if you could give me a heads I would really appreciate it.

          Comment


          • #6
            Originally posted by drubio View Post
            Thanks.
            Originally posted by drubio View Post
            I upgraded to Spring 3.0, but now I'm getting what appears to be a Spring 3.0 related error.

            Any idea if this particular package/class ceased to exist or changed name from 2.5 to 3.0? Or perhaps just a missing dependency (Export) in the 3.0.0.CI-217 milestone release used by the dm Server ?
            I guess I could post to the general Spring 3.0 section, but if you could give me a heads I would really appreciate it.
            This looks like a bug. Please see my response to your other post.

            Comment

            Working...
            X