3 Oct 2011 17:58
MultiThread dispatcher
Hello, I'm using SNMP4J 1.11.2. I use one SNMP instance with multithread dispatcher (thread pool 20). My manager can be connected to 1500 agents using snmpv3 over TCP. I checked that on some occasions, the notifications of a specific agent can be processed in a different order that the one sent by the agent. Below one can see an example of such a case. The threadpool name is "SNMP Dispatcher". So from this example I can see that notification with sysupTime = 4 days, 0:09:55.97 has reached my manager before the other one with a earlier time (4 days, 0:09:55.93). I can see also that each notification reached my manager by a different thread (SNMP Dispatcher.0, SNMP Dispatcher.1). The problem is that using an SNMP instance for each agent (singlethreaded) I can end up with thousands of threads that don't work most of the time. It's a waste of resources. My question: is there a way to avoid this issue? (beside using one snmp instance for each target) Thanks KREgards, RAR Example: 15:43:47,206 DEBUG SNMP Dispatcher.0 [SNMP] Processing PDU(Continue reading)
RSS Feed