Announcement Announcement Module
Collapse
No announcement yet.
.par not deploying on beta3 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • .par not deploying on beta3

    Dont ask me why, but the app (.par) which deploys on beta3 does not deploy on beta3 for me.

    Hope this log helps

    [2008-05-23 15:13:59.723] fs-watcher <SPDE0010I> Deployment of 'platform.admin.splash-1.0.0.beta3.war' version '0' completed.
    [2008-05-23 15:14:24.685] platform-tomcat-thread-1 <SPSC1000I> Creating web application '/id'.
    [2008-05-23 15:14:55.037] platform-tomcat-thread-1 <SPDE0040E> Deployment of module 'file [/home/tmaus/server/springsource-ap-1.0.0.beta3/work/com.springsource.platform.deployer/Module/com.steademy.service.is-0.1/com.steademy.service.is.identity-web-0.1.0.war]' took too long and timed out.
    [2008-05-23 15:14:55.344] platform-tomcat-thread-1 <SPDE0011E> Deployment failed.
    com.springsource.platform.deployer.core.Deployment Exception: Deployment of 'file [/home/tmaus/server/springsource-ap-1.0.0.beta3/work/com.springsource.platform.deployer/Module/com.steademy.service.is-0.1/com.steademy.service.is.identity-web-0.1.0.war]' failed due to time out
    at com.springsource.platform.deployer.core.module.Sta ndardModule.checkDeployed(StandardModule.java:264)
    at com.springsource.platform.deployer.app.OsgiApplica tion.deploy(OsgiApplication.java:180)
    at com.springsource.platform.deployer.core.internal.S tandardApplicationDeployer.deploy(StandardApplicat ionDeployer.java:390)
    at com.springsource.platform.deployer.core.internal.S tandardApplicationDeployer.deploy(StandardApplicat ionDeployer.java:348)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.osgi.service.importer.internal .aop.ServiceInvoker.doInvoke(ServiceInvoker.java:5 9)
    at org.springframework.osgi.service.importer.internal .aop.ServiceInvoker.invoke(ServiceInvoker.java:67)
    at org.springframework.aop.framework.ReflectiveMethod Invocation.proceed(ReflectiveMethodInvocation.java :171)
    at org.springframework.aop.support.DelegatingIntroduc tionInterceptor.doProceed(DelegatingIntroductionIn terceptor.java:131)
    at org.springframework.aop.support.DelegatingIntroduc tionInterceptor.invoke(DelegatingIntroductionInter ceptor.java:119)
    at org.springframework.aop.framework.ReflectiveMethod Invocation.proceed(ReflectiveMethodInvocation.java :171)
    at org.springframework.osgi.service.importer.support. LocalBundleContextAdvice.invoke(LocalBundleContext Advice.java:59)
    at org.springframework.aop.framework.ReflectiveMethod Invocation.proceed(ReflectiveMethodInvocation.java :171)
    at org.springframework.aop.support.DelegatingIntroduc tionInterceptor.doProceed(DelegatingIntroductionIn terceptor.java:131)
    at org.springframework.aop.support.DelegatingIntroduc tionInterceptor.invoke(DelegatingIntroductionInter ceptor.java:119)
    at org.springframework.aop.framework.ReflectiveMethod Invocation.proceed(ReflectiveMethodInvocation.java :171)
    at org.springframework.aop.framework.JdkDynamicAopPro xy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy86.deploy(Unknown Source)
    at com.springsource.platform.servlet.admin.service.im pl.StandardApplicationManagerService.deploy(Standa rdApplicationManagerService.java:100)
    at com.springsource.platform.servlet.admin.web.Applic ationManagerController.deploy(ApplicationManagerCo ntroller.java:81)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.web.servlet.mvc.multiaction.Mu ltiActionController.invokeNamedMethod(MultiActionC ontroller.java:473)
    at org.springframework.web.servlet.mvc.multiaction.Mu ltiActionController.handleRequestInternal(MultiAct ionController.java:410)
    at org.springframework.web.servlet.mvc.AbstractContro ller.handleRequest(AbstractController.java:153)
    at org.springframework.web.servlet.mvc.SimpleControll erHandlerAdapter.handle(SimpleControllerHandlerAda pter.java:48)
    at org.springframework.web.servlet.DispatcherServlet. doDispatch(DispatcherServlet.java:875)
    at org.springframework.web.servlet.DispatcherServlet. doService(DispatcherServlet.java:809)
    at org.springframework.web.servlet.FrameworkServlet.p rocessRequest(FrameworkServlet.java:571)
    at org.springframework.web.servlet.FrameworkServlet.d oPost(FrameworkServlet.java:511)

  • #2
    .par not deploying on beta3

    some more information.

    My web - bundle does not start on beta3 and beta4 but properly loads in beta2.

    Log excerpt:

    [2008-05-29 13:25:12.652] platform-tomcat-thread-1 ce.platform.deployer.core.internal.StandardDeploye rConfiguration < int com.springsource.platform.deployer.core.internal.S tandardDeployerConfiguration.getDeploymentTimeoutS econds()
    [2008-05-29 13:25:22.607] async-delivery-thread-1 .core.internal.ApplicationContextRetrievingAndPubl ishingCallback E <SPWE1001E> Failed to create web application '/id': the associated web bundle 'com.steademy.service.is-0.1.1-com.steademy.service.is.web' failed to publish its ApplicationContext within 10000 seconds.
    [2008-05-29 13:25:22.609] async-delivery-thread-1 urce.platform.deployer.core.module.StandardModule. onStarted(490) E onStarted of module 'file [/home/tmaus/server/springsource-ap-1.0.0.beta4/work/com.springsource.platform.deployer/Module/com.steademy.service.is-0.1.1/identity-web.war]' caught an exception
    com.springsource.platform.deployer.core.Deployment Exception: Timeout while waiting for web bundle 'com.steademy.service.is-0.1.1-com.steademy.service.is.web'
    at com.springsource.platform.web.core.internal.Applic ationContextRetrievingAndPublishingCallback.preCon textDeployment(ApplicationContextRetrievingAndPubl ishingCallback.java:126)
    at com.springsource.platform.web.core.WebModulePerson ality.deploy(WebModulePersonality.java:347)
    at com.springsource.platform.deployer.core.module.Abs tractModule.deploy(AbstractModule.java:226)
    at com.springsource.platform.deployer.core.module.Sta ndardModule.onStarted(StandardModule.java:484)
    at com.springsource.platform.deployer.core.module.Dep loyerBundleListener$2$1.run(DeployerBundleListener .java:148)
    at com.springsource.platform.concurrent.core.Executor ServiceDelegate$StatisticsGatheringRunnable.run(Ex ecutorServiceDelegate.java:136)
    at com.springsource.platform.concurrent.core.Platform ThreadPoolExecutor$1.run(PlatformThreadPoolExecuto r.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:885)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:907)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.util.concurrent.TimeoutException: Timeout while waiting.
    at com.springsource.platform.kernel.core.internal.App licationContextFuture.get(ApplicationContextFuture .java:120)
    at com.springsource.platform.kernel.core.internal.App licationContextFuture.get(ApplicationContextFuture .java:1)
    at com.springsource.platform.web.core.internal.Applic ationContextRetrievingAndPublishingCallback.preCon textDeployment(ApplicationContextRetrievingAndPubl ishingCallback.java:117)
    ... 9 more

    [2008-05-29 13:25:22.611] async-delivery-thread-1 com.springsource.platform.deployer.core.module.Sta ndardModule E <SPDE0025E> Exception after module 'file [/home/tmaus/server/springsource-ap-1.0.0.beta4/work/com.springsource.platform.deployer/Module/com.steademy.service.is-0.1.1/identity-web.war]' started.
    com.springsource.platform.deployer.core.Deployment Exception: Timeout while waiting for web bundle 'com.steademy.service.is-0.1.1-com.steademy.service.is.web'
    at com.springsource.platform.web.core.internal.Applic ationContextRetrievingAndPublishingCallback.preCon textDeployment(ApplicationContextRetrievingAndPubl ishingCallback.java:126)
    at com.springsource.platform.web.core.WebModulePerson ality.deploy(WebModulePersonality.java:347)
    at com.springsource.platform.deployer.core.module.Abs tractModule.deploy(AbstractModule.java:226)
    at com.springsource.platform.deployer.core.module.Sta ndardModule.onStarted(StandardModule.java:484)
    at com.springsource.platform.deployer.core.module.Dep loyerBundleListener$2$1.run(DeployerBundleListener .java:148)
    at com.springsource.platform.concurrent.core.Executor ServiceDelegate$StatisticsGatheringRunnable.run(Ex ecutorServiceDelegate.java:136)
    at com.springsource.platform.concurrent.core.Platform ThreadPoolExecutor$1.run(PlatformThreadPoolExecuto r.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:885)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:907)
    at java.lang.Thread.run(Thread.java:619)
    :
    has anyone already came across this problem ???

    Comment


    • #3
      .par not deploying on beta3

      Hi Thorsten,

      From the log message, we can see that your web module is failing to start because it is not publishing its application context within 10 seconds. This could happen for one of two reasons:

      1) the application context start-up simply takes longer than 10 seconds, in which case the timeout is too short for your application.

      2) an error occurred during application context start-up which prevented it from being published.

      In case of #1, there is nothing you can do with pre-beta5 releases. In case of #2, the best you can do with pre-beta5 releases is to wade through the trace to determine what went wrong; however, in the next release (i.e., beta5) we will be providing better failure diagnostics for application context start-up and publication. In addition, the timeout for web modules is now set to the global deployment timeout value which is configurable.

      Regards,

      Sam

      Comment


      • #4
        .par not deploying on beta3

        ok ... tracked down the problem as far as possible (without building platform from source and debugging it )

        let me summarize:

        our application properly runs on beta2.

        We deploy two bundles,
        an infrastructure bundle
        and an application bundle that contains of:
        -> api
        -> domain
        -> app
        -> web

        As shown in the log the depoloyment fails within the web artifact.
        Thus I tried to narrow down the problem by removing ALL osgi references within the beans context.
        <osgi:reference id="identityService" interface="la.lup.IdentityService"/>

        As a consequence the application properly deploys.

        It might sound a bit strange but at least in my case the osgi references within the web-artifact cause the timeout exceptions.

        Any idea ???

        Comment


        • #5
          .par not deploying on beta3

          some more information ..

          the deployment problem still exists with beta5 as well ..

          I was able to narrow the problem down a bit ..

          Our application consists of two main packages, the infrastructure as well as the service itself.
          the infrastructure is deployed prior the service.

          Deploying the service ends up in a timeout-exception ( as mentioned before )

          The important lines of the log are:
          [2008-06-01 12:27:26.947] platform-dm-8 r.internal.dependencies.startup.DependencyServiceM anager.unknown I Adding OSGi service dependency for importer &hibernateProperties
          [2008-06-01 12:27:26.948] platform-dm-8 springsource.platform.kernel.dm.ContextPropagating TaskExecutor$2 < void com.springsource.platform.kernel.dm.ContextPropaga tingTaskExecutor.2.run()
          [2008-06-01 12:27:28.927] platform-tomcat-thread-1 current.core.ExecutorServiceDelegate$StatisticsGat heringRunnable < void com.springsource.platform.concurrent.core.Executor ServiceDelegate.StatisticsGathering
          Runnable.run()
          [2008-06-01 12:27:28.927] platform-tomcat-thread-1 ncurrent.core.PlatformThreadPoolExecutor$Applicati onNameAccessor > void com.springsource.platform.concurrent.core.Platform ThreadPoolExecutor.ApplicationNameA
          ccessor.setCurrentApplicationName(String)
          [2008-06-01 12:27:28.927] platform-tomcat-thread-1 ncurrent.core.PlatformThreadPoolExecutor$Applicati onNameAccessor < void com.springsource.platform.concurrent.core.Platform ThreadPoolExecutor.ApplicationNameA
          ccessor.setCurrentApplicationName(String)
          [2008-06-01 12:27:28.928] platform-tomcat-thread-1 ringsource.platform.concurrent.core.PlatformThread PoolExecutor$1 < void com.springsource.platform.concurrent.core.Platform ThreadPoolExecutor.1.run()

          The hibernateProperties is an osgi service properly deployed to the osgi platform:
          A reference to it is defined in our beans configuration and looks like:
          <osgi:reference id="hibernateProperties" interface="java.util.Properties"/>

          The deployed infrastructure bundle inside osgi platform reveals:
          osgi> bundle 81
          file:////home/tmaus/server/springsource-ap-1.0.0.beta5/work/com.springsource.platform.deployer/Module/com.steademy.service.infrastructure-0.2/hsqldb-datasource.jar [81]
          Id=81, Status=ACTIVE Data Root=/home/tmaus/server/springsource-ap-1.0.0.beta5/work/equinox-config/org.eclipse.osgi/bundles/81/data
          Registered Services
          {javax.sql.DataSource}={org.springframework.osgi.b ean.name=dataSource, Bundle-SymbolicName=com.steademy.service.infrastructure-0.2-com.steademy.service.infrastructure.hsqldb, Bundle-Version=1.0.0, com.springsource.platform.app.name=com.steademy.se rvice.infrastructure-0.2, service.id=94}
          {java.util.Properties}={org.springframework.osgi.b ean.name=hibernateProperties, Bundle-SymbolicName=com.steademy.service.infrastructure-0.2-com.steademy.service.infrastructure.hsqldb, Bundle-Version=1.0.0, com.springsource.platform.app.name=com.steademy.se rvice.infrastructure-0.2, service.id=95}
          {org.springframework.osgi.context.DelegatedExecuti onOsgiBundleApplicationContext, org.springframework.osgi.context.ConfigurableOsgiB undleApplicationContext, org.springframework.context.ConfigurableApplicatio nContext, org.springframework.context.ApplicationContext, org.springframework.context.Lifecycle, org.springframework.beans.factory.ListableBeanFact ory, org.springframework.beans.factory.HierarchicalBean Factory, org.springframework.context.MessageSource, org.springframework.context.ApplicationEventPublis her, org.springframework.beans.factory.BeanFactory, org.springframework.core.io.ResourceLoader, org.springframework.beans.factory.DisposableBean}= {org.springframework.context.service.name=com.stea demy.service.infrastructure-0.2-com.steademy.service.infrastructure.hsqldb, Bundle-SymbolicName=com.steademy.service.infrastructure-0.2-com.steademy.service.infrastructure.hsqldb, Bundle-Version=1.0.0, service.id=96}

          I think that this information should narrow down the problem.
          Is it possible that starting with beta3 the deployer has problems referencing services that have been deployed earlier ??

          Again, i deployed two services, the infrastructure as well as a personal service.
          The personal service references the infrastructure service
          During the deployment of the personal service I receive a timeout exception at the aformentioned position.

          Both service properly deploy on beta2 .

          :O)

          thanks for your patience ...

          Comment


          • #6
            .par not deploying on beta3

            the hibernateProperties definition looks like:

            <osgi:service ref="hibernateProperties" interface="java.util.Properties"/>

            <bean id="hibernateProperties" class="org.springframework.beans.factory.config.Pr opertiesFactoryBean">
            <property name="properties">
            <props>
            <prop key="hibernate.dialect">${hibernate.dialect}</prop>
            <prop key="hibernate.cache.use_query_cache">${hibernate. cache.use_query_cache}</prop>
            <prop key="hibernate.cache.use_second_level_cache">${hib ernate.cache.use_second_level_cache}</prop>
            <prop key="hibernate.show_sql">${hibernate.show_sql}</prop>
            <prop key="hibernate.connection.release_mode">auto</prop>
            <prop key="hibernate.hbm2ddl.auto">${hibernate.hbm2ddl.a uto}</prop>
            <!--
            <prop key="hibernate.cache.provider_class">${hibernate.c ache.provider_class}</prop>
            <prop key="hibernate.current_session_context_class">${hi bernate.current_session_context_class}</prop>
            <prop key="hibernate.query.substitutions">${hibernate.qu ery.substitutions}</prop>
            -->
            </props>
            </property>
            </bean>

            Comment


            • #7
              .par not deploying on beta3

              Thorsten,

              Is it possible to send us this application, or at least a small portion of it so we can try this out?

              The best avenue for this is to attach it to a JIRA report.

              Regards,

              Rob

              Comment

              Working...
              X