Configuring Timeout

Normal Invocation Timeout

The CLI times out if the CLI action cannot be finished by the specified time. By default, no timeout is set. This timeout value can be specified in two ways using the timeout attribute:

• In the ANT target

  For example, to set the timeout to 60 seconds, set the following timeout attribute.

  <target name="deploy-applications">
  <AMXAdminTask 
  action="deploy" 
  objectSelector="Environment//Application" 
  remote="true" 
  propsFile="${instanceProperties}" 
  dataFile="${dataFile}" 
  force="true" 
  failOnError="true" 
  timeout="60"/> 
  </target>

  The unit for the timeout is seconds.

• In the remote_props.properties file

  For example, to set the timeout to 60 seconds, add the following timeout attribute.

  adminURL=http://localhost:8120
  username=root
  password=
  httpConnectionTimeout=360000
  timeout=60

  The unit for the timeout is seconds. This option can be used to set the timeout value for all ANT targets, without having to specify the timeout value in each Ant target separately).

  Note: The timeout value set in the Ant target takes precedence over the value set in the remote_props.properties file.

No progress timeout

The CLI times out if there is no progress on processing the tasks within the specified time. To specify the "no progress timeout", set the property com.tibco.admin.cli.noprogress.timeoutInMinutes in the SystemNode's TRA file. The unit for the timeout is minutes.

For example, to set the "no progress timeout" to 30 minutes, set the property as follows:

java.property.com.tibco.admin.cli.noprogress.timeoutInMinutes = 30

To disable the property, set the value to 0. The default value for "No progress timeout" is 45 minutes.