Deployment of JBoss ON bundle is aborted if it takes more then 4 hours to deploy

Solution Unverified - Updated

Environment

  • Red Hat JBoss Operations Network (ON) 3.1.2, 3.2
  • Deploying a JBoss ON provisioning bundle
  • Provisioning bundle recipe takes over 4 hours to execute

Issue

  • Timeout during bundle deployment
  • Deploy keeps timing out
  • Change or disable 4 hour timeout
  • Deployment failed: org.rhq.core.pc.inventory.TimeoutException:Call to [org.rhq.plugins.ant.AntBundlePluginComponent.deployBundle()]
  • Deployment of bundle fails due to timeout

Resolution

The provisioning bundle recipe should be rewritten to ensure that it completes in less then four (4) hours. The 4 hour time limit can not be adjusted or disabled.

It may be necessary to use the Ant exec task to execute an external script in the background which performs the long running tasks. This will allow the bundle's deployment operation to finish well within the maximum 4 hour time limit.

Root Cause

The JBoss ON Ant agent plug-in which is responsible for executing the deploy request limits the execution to 4 hours. This timeout is built-in to the plug-in and is not configurable.

Although this is by design, This content is not included.Red Hat Bugzilla 1165399 has been captured asking for this timeout to be configurable.

SBR
Product(s)
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.