Red Hat Bugzilla – Bug 982804
AS7 reload behavior includes hardcoded timeout of 20 seconds
Last modified: 2014-01-02 15:37:45 EST
Description of problem:
AS7 reload operation fails if the management interface takes longer than 20 seconds to come back up after the reload due to a hardcoded timeout in org/rhq/modules/plugins/jbossas7/StandaloneASComponent.java in the waitUntilReloaded() method.
Version-Release number of selected component (if applicable):
JBoss ON 3.1.2
Steps to Reproduce:
Issue will present itself only if there is a delay in the startup that prevents the management interface from coming up in less than 20 seconds. In that case, the issue can be reproduced by issuing the "Reload" operation, waiting 20 seconds, and observing the failure of the operation in the operation history.
Reloads that take longer than 20 seconds are reported as failures.
Reload operation should report the correct result. This should most likely be through a configurable timeout or a repurpose of the BaseServerComponent.waitForServerToStart() method.
This is similar to the issue reported in BZ 966777.
Fixed in master
Author: Thomas Segismont <email@example.com>
Date: Tue Jul 16 13:42:50 2013 +0200
As this is MODIFIED or ON_QA, setting milestone to ER1.
verified on ER5. I was not able to reproduce when EAP6 takes more than 20s to reload, although fix oboviously removes hardcoded timeout and relies on general operation timeout .