Frank, I agree with you that this may yield a very small benefit as it is just protecting against a theoretical agent bug. In fact, after thinking about it some more, it may not even be worth incurring the extra cost of synchronization to protect against such agent bugs.
Thanks for your time. Regards, Syed Syed F. Ali CA Technologies Sr Software Engineer Tel: +1 603 334 2111 syed.al...@ca.com -----Original Message----- From: Frank Fock <f...@agentpp.com> Subject: Re: [SNMP4J] help - possible thread-unsafe code in snmp4j To: snmp4j@agentpp.org Message-ID: <51100277.4080...@agentpp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi Syed, Yes, it is true, that if an agent sends multiple reports concurrently and a multi-threaded message dispatcher is used, more than "request.maxRequestStatus" reports could be send back, because reading and incrementing the request status is not synchronized. However, this only happens if the agent violates the protocol or is misconfigured (sending retries in very short intervals). I will add a synchronization on the request.requestStatus for the next release - although I see only a very small benefit. Best regards, Frank _______________________________________________ SNMP4J mailing list SNMP4J@agentpp.org http://lists.agentpp.org/mailman/listinfo/snmp4j
