BMC BladeLogic Application Release Automation - How to increase MAX TIME OUT setting to avoid "The task timed out" errors during app deployment

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC BladeLogic Application Release Automation - Standard


    APPLIES TO:

    BMC BladeLogic Application Release Automation - Standard



    PROBLEM:

     

    Problem Description:

      

    How do I increase the MAX TIME OUT setting in BMC BladeLogic Application Release Automation to avoid "The task timed out" errors during app deployment?
    OR
    Application deployment hangs at "Installing MBean Application" and then errors out.

    LP: BMC BladeLogic Application Release Automation
    DR: BMC BladeLogic Application Release Automation

     


    SOLUTION:

     

    Legacy ID:KA353498

      

    The Default value for MAXTASKWAIT is set to 120 seconds, but depending on various factors, like the size of EAR/WAR file is big or there is a network latency between the ARA HOST and the Target Application Server HOST, then the app deployment might TIME OUT during deployment after 120 seconds.

      

    Below is a snippet of the error which can be seen in the phurnace.log when an AppDeployment failed because the MAXTASKWAIT has exceeded the assigned value:

    (The phurnace.log can be found on WORKSPACE/working/<TimeStamped_Folder> for Graphical User Interface (GUI) operations and on the ARA-INSTALL_HOME/cli/<TimeStamped_Folder> for Command Line Interface (CLI) operations.)

      

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    28 Oct 2011 11:58:41 - INFO - (AbstractWebSphereEngine.java:1029) - Installing MBean Application
    (If the logging level is set to INFO then the logs would stop at a point as shown above. Change the logging level to DEBUG to see detailed messages))

    (If the logging level is set to DEBUG then the logs would be in detail where you can see it waited for 120 seconds and failed as below)
    28 Oct 2011 11:58:44 - DEBUG - (MBeanServerFacade.java:2613) - Waiting up to 118 sec
    28 Oct 2011 11:58:44 - DEBUG - (MBeanServerFacade.java:2613) - Waiting up to 120 sec
    28 Oct 2011 11:58:45 - ERROR - (MBeanServerFacade.java:2621) - The task timed out
    28 Oct 2011 11:58:45 - ERROR - (AbstractEngine.java:968) - Exception Name: WebSphere:Name=XXXXXXXXXCell01,Type=Cell:Application
    28 Oct 2011 11:58:45 - ERROR - (AbstractEngine.java:969) - Exception Message: The task timed out
    28 Oct 2011 11:58:45 - ERROR - (AbstractEngine.java:971) - Exception Class: com.phurnace.exception.PhurnaceException
    28 Oct 2011 11:58:45 - ERROR - (AbstractEngine.java:972) - Stack Trace:
    com.phurnace.exception.PhurnaceException: The task timed out
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

      


    Follow the below steps to increase the MAXTASKWAIT time from default 120 seconds to a higher value.

    For GUI Operations
    1. In the ARA UI, select Window -> Preferences -> BMC Application Release -> Launcher Properties.

    2. Add a launcher property as described below.

    Name: jvmarg.phurnace.maxTaskWait
    Value: -Dphurnace.maxTaskWait="300000"

      

    NB: The Value is given in milli-seconds.

    For CLI Operations
    1. From the ARA _INSTALL_HOME/cli, open setupDeliver.properties in a text editor

    2. At the bottom of the setupDeliver.properties, change the following lines.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    FROM:

      

    JVMARGS=

      

    TO:

      

    JVMARGS= -Dphurnace.maxTaskWait="300000"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 

      

    NB: The Value is given in milli-seconds.

      
    Related Products:  
       
    1. BMC BladeLogic Application Release Automation - Standard

     


    Article Number:

    000094400


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles