Hide Forgot
Description of problem: EAP6 plugin ignores rhq.agent.plugins.availability-scan.timeout setting and defaults to 10 seconds. If you increase the agent's availability scan timeout setting to 15 seconds the availability timeout on an EAP 6 server still remains at 10 seconds. The plug-ins method execution timeout isn't using the agent's availability timeout setting and should be. Version-Release number of selected component (if applicable): 3.1.2 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
It actually is defaulting to 5 seconds, not 10
I can confirm that the timeout is currently 10 seconds. This is the default for all AS7 operations. Very few operations have this timeout overridden or overridable. The avail check is done via :read-resource operation. The requested change would need to be implemented across the board for availability checks of all AS7 resources, since there is not much gain if just some components get a configurable timeout. Also this is a shared setting, so changes to the setting itself will affect all other plugins that use it (eg. apache plugin).
Re-targeted to CP02 to reduce CP01 overall payload.
The change is now merged into the release/jon3.2.x branch. Here are the details of the implemented fix: 1) use container avail timeout for sync avail checks 2) fix the usage plugin configuration settings for async avail for server components release/jon3.2.x branch commit: https://github.com/rhq-project/rhq/commit/2ef9ad2dd2af728af3817baf946089b512609bc3
Moving this back to MODIFIED. Not yet available for QA until available in next productized build. Setting target to DR02.
Moving this bug to: One-Off release as is EAP plugin pack update block BZ 1088652 which tracks the next EAP plugin pack update release.
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993