[SNMP4J] Received response that cannot be matched to any outstanding request !

[Frank Fock]

Hi Varma,

Have you tried to increase the timeout value?
Also consider UDP buffer sizes. That is, when
sending many requests in short time, then there
could be UDP buffer overflows.

Another common error is reusing PDUs between
concurrent requests without cloning the PDU/request
ID.

Best regards,
Frank

varma datla wrote:
> Hi,
> We are using snmp4j (1.7.6 and multi-threaded) to find devices in a network. The following warning is appearing in the log files and ultimately unable to find these devices. It is working fine when used a single thread to find these devices.
> 
> This warning is not consistent for each run (different devices each time). 
> Is this a bug? or could you please tell me in what situation does this warning appears?
> 
> [DefaultUDPTransportMapping_HOST_IP] WARN  org.snmp4j.Snmp  - Received response that cannot be matched to any outstanding request, address=TARGET_IP, requestID=2064633714
> [DefaultUDPTransportMapping_HOST_IP] WARN  org.snmp4j.Snmp  - Received response that cannot be matched to any outstanding request, address=TARGET_IP, requestID=2064633714
> 
> Thanks in advance.
> 
> Varma.
>  		
> ---------------------------------
> Stay in the know. Pulse on the new Yahoo.com.  Check it out. 
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/snmp4j

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com