1 Reply Latest reply on Apr 20, 2012 2:24 PM by 931553

    DeploymentService:290051  How to increase the default Deployment timeout

      I am trying to profile application startup in Weblogic 10.3. Profiling makes the application startup very slow, which is ok, I don't mind it taking a few hours to startup. It appears that after 1 hour Weblogic deployment timeout happens, and kills the start up. See the log below.
      How can I increase this timeout?
      I found Weblogic release notes on http://e-docs.bea.com/workshop/docs92/relnotes/relnotes.html (item CR299479) talking about weblogic.deployment.timeout as a global system property. I tried it in JVM args with a value of 7200000 (2 hours in milliseconds), but it didn't help.

      ####<28-Feb-2009 8:43:10 o'clock AM EST> <Info> <J2EE Deployment SPI> <xxxxxx> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1235828590128> <BEA-260121> <Initiating start operation for application, webapp [archive: null], to AdminServer .>
      ####<28-Feb-2009 8:43:15 o'clock AM EST> <Info> <Deployer> <xxxxxxxx> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1235828595236> <BEA-149038> <Initiating Task for bpsproject : [Deployer:149026]start application webapp on AdminServer.>
      .............NOTE: after 1 hour.................
      ####<28-Feb-2009 9:43:16 o'clock AM EST> <Notice> <DeploymentRequestTimeoutLogger> <xxxxxxx> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1235832196298> <BEA-000000> <[DeploymentService:290051]The commit message for the deployment '1,235,828,594,718' could not be completed because the deployment timed out. : Targets to respond : [AdminServer]>

      If anyone knows how to increase this application startup/deployment timeout in Weblogic 10.3, please let me know.
      Thank you!!