[SNMP4J] Matching outstanding request

[Frank Fock]

Hi Mathias,

Possible reasons for unmatched responses could be indeed too short timeouts.
By increasing the number of retries, you cannot reduce the likelihood of
unmatched responses, in contrary is true. Because there are many agent
implementations that do not differentiate retries from other requests.
Such agents return a response on any request, regardless whether it
is a retry or a regular request. Other agents, like AGENT++ based agents
detect retries while they process a request but those agents cannot
detect retries of an already answered request.

A UDP buffer overflow also cannot be the reason of unmatched
responses, because in such a case, the response will gets lost and the
application will never be able recognize the response at all.

Thus, to reduce unmatched response:
(a) reduce to number of retries (i.e. set it to 0)
(b) increase the timeout.

Hope this helps.

Best regards,
Frank

Mathias Bogaert wrote:

> Hi,
>
> I'm frequently getting these warnings:
>
> 493603 WARN  [Thread-155] - Received response that cannot be matched 
> to any outstanding request, address=10.244.66.22/161, requestID=455811452
>
> What could be the cause of this? Too short timeouts? Zero retries? A 
> UDP buffer overflow on the Solaris machine (buffer size is already 
> 2048 kb).
>
> Thank you,
>
> Mathias Bogaert
>
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> http://p15141779.pureserver.info/mailman/listinfo/snmp4j
>