Red Hat Bugzilla – Bug 864255
[apache plugin] SNMP ping timeout is too low (50ms) and is not configurable
Last modified: 2013-09-11 06:59:41 EDT
+++ This bug was initially created as a clone of RHQ Bug #813361 +++
The following message appears in the Agent log if an Apache Server avail check fails due to the SNMP "ping" timing out:
2012-04-11 17:44:56,271 DEBUG [ResourceContainer.invoker.daemon-102] (rhq.plugins.www.snmp.SNMPSession_v2c)- Error while pinging SNMP 1 agent at 127.0.0.1/1610/public. SNMP GETNEXT request for iso(1) failed - org.rhq.plugins.www.snmp.SNMPException: Request for [iso] timed out.
Looking at the code, the SNMP timeout that's used is 50ms (with 1 retry) and is not configurable, so I'm not surprised it's timing out every so often... 50ms seems way low to me.
I think we should do the following:
1) increase the default value for the timeout to 4s so it's just under the default avail facet timeout
2) change the default retries from 1 to 0
3) make the timeout and the retries configurable via conn props
--- Additional comment from email@example.com on 2012-04-18 12:40:51 EDT ---
Done in master:
Here are the two new props that have been added to the Apache Server type's plugin config:
<c:simple-property name="snmpRequestTimeout" displayName="SNMP Request Timeout" type="long" default="2000" required="false"
description="the timeout, in milliseconds, for requests to the Apache SNMP agent; defaults to 2000">
<c:simple-property name="snmpRequestRetries" displayName="SNMP Request Retries" type="integer" default="1" required="false"
description="the number of times a request that has timed out should be retried; defaults to 1">
Moving to ON_QA as this was added to master back in April but just needs to be tested in a release (was introduced in JON 3.1)
Verified on JON 3.1.2.ER1 build.
The Apache connection properties shows the fields 'SNMP Request Timeout' with default value as 2000 ms and 'SNMP Request Retries' with default value as 1. Verified that the fields can be modified and saved successfully.
Also verified the field validations and validations for min values for the properties.