Might be Related to ???? [SNMP4J] Unnecessary SNMP retries after a response hasbeen received ?

[Richard Tarczaly]

Hi Frank,

This issue might be related to the previous message : 
"[SNMP4J] Unnecessary SNMP retries after a response has been received ?"

Sometimes I get two request replies for a single request (only 1
snmp.SEND for sure, did not put an Ethereal on it to actually make sure
how many requests leave to the network).

Since I have a MultiThreadedMessageDispatcher, the second req-reply will
randomly go to a (and obviously incorrect) responder, as the responder
registered to deal a req-reply is no more (already did it's job on the
first req-reply).

The responder is obviously not the one registered to deal with the
req-reply, as it is registered for a different request and hence waits
for a different req-reply.

Any idea to what might go wrong ? 

I changed the send method with the one you suggested and will run tests
in a short while. If this strange behavior shows up again I will let you
know.

Thank you in advance,
Richard


Richard Tarczaly
__________________________
Software Architect
DAX Technologies Corp.
Matawan, New Jersey, 07747, U.S.
Tel:       (732) - 203 - 1784 x 114
Mobile:  (908) - 601 - 0616
Fax:      (732) - 203 - 1786
E-mail:  ricky at daxtechnologies.com