Description of problem:
JBoss ON reports start/stop operation for EAP 6 as failed if it takes longer then 20 seconds to start or stop the server.

This results in inconsistent and incorrect results being reported for operations and those operations prematurely being aborted in the event that the user has explicitly set a timeout.

Version-Release number of selected component (if applicable):
4.4.0.JON312GA

How reproducible:
Always

Steps to Reproduce:
1.  Install JON system.
2.  Import EAP 6 standalone server into inventory.
3.  Shutdown EAP standalone resource.
4.  Modify standalone.sh to include a 60 second sleep after the export JAVA_HOME command:

        sed -i 's/^export JBOSS_HOME$/export JBOSS_HOME\nsleep 60/' "${JBOSS_HOME}/bin/standalone.sh"
        
5.  From JBoss ON, invoke the EAP resource's start operation.

Actual results:
The operation will report failure well before the default 10 minute operation timeout setting.

Expected results:
The operation should report success after approximately 1 minute.

Additional info:
As indicated by Marc in the support ticket, this is due to using hard-coded values in the BaseServerComponent.waitUntilDown() and BaseServerComponent.waitForServerToStart() methods. Specifically, we loop 20 times with a one second sleep between state checks and then error out.

Considering that there is a concept of an operation timeout utilized by the plug-in container and defined by the agent configuration with an option to override it when an operation is invoked, this seems like a major oversight. We should not be using hard coded configuration values anywhere in the code and especially when dealing with execution logic that is controlled by user configuration.