Hi,
I cannot follow your writing. An INFORM PDU is always a
confirmed PDU. Also I cannot see why there should be
two messages send for any PDU (other than retries).
Best regards,
Frank
On 04.08.2011 20:20, Beau Anderson wrote:
> I'm new to this mailing list list so I don't know if this has been covered
> yet. If so, I apologize.
>
> This is a bug report. Using SNMP4j v1.11.3 if you send an SNMP v3 Inform and
> pdu.isConfirmedPdu() returns false then it creates an asynchronous pending
> request and registers a timer for it then it also performs a synchronous send
> on the inform. The result is that duplicate messages are sent a few seconds
> apart from each other.
>
> The relevant code is in MessageDispatcherImpl lines 458 - 462:
>
>
>
> 458 if (pduHandleCallback != null) {
> 459 pduHandleCallback.pduHandleAssigned(pduHandle, pdu);
> 460 }
> 461 byte[] messageBytes = outgoingMessage.getBuffer().array();
> 462 sendMessage(transport, transportAddress, messageBytes);
>
>
> Line 462 should not get called on asynchronous calls.
> _______________________________________________
> SNMP4J mailing list
> [email protected]
> http://lists.agentpp.org/mailman/listinfo/snmp4j
--
AGENT++
http://www.agentpp.com
http://www.snmp4j.com
http://www.mibexplorer.com
http://www.mibdesigner.com
_______________________________________________
SNMP4J mailing list
[email protected]
http://lists.agentpp.org/mailman/listinfo/snmp4j
