[SNMP4J] Unnecessary SNMP retries after a response has been received ?

[Frank Fock]

Hello,

Are you using sync or async requests? If you use the latter,
are you calling Snmp.cancel(PDU request, ResponseListener listener)
when your callback method has been called?

Thanks,
Frank

koen.janssens at alcatel.be wrote:
> Hello
> 
> I'm sending an SNMP message with retry value of 3. 
> 
> The agent react slow (say: the response time is twice the snmp timeout 
> used by the client).  So the client sends the first message, times out, 
> sends the second message. After that is receives a response. (from the 
> first request). I would expect that the client would stop here, but it 
> seems that he sends the third retry anyhow, although he already received 
> an answer. 
> 
> I played a bit with it and it seems that as soon as one retry is send, the 
> client will send ALL the retries, wheter or not the server replies in 
> between. 
> I dived in the code and I think it's related to the fact that a new 
> PendingRequest instance is created for each retry, but only the first one 
> is set to 'finished' in case a response arrives.
> 
> I'm using SNMP4j 1.6d
> _______________________________________________
> 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