I am using MultiThreadedMessageDispatcher together with AgentConfigManager.
If I give a workerPool to MultiThreadedMessageDispatcher but not to AgentConfigManager, then incoming requests are threading fine but Notifications are serialized. If I give a workerPool to MultiThreadedMessageDispatcher and AgentConfigManager, then notifications can be sent in parallel but incoming requests go through excessive thread switching. The request starts on the transport thread, then hops to a MultiThreadedMessageDispatcher and finally hops again to an AgentConfigManager thread. The first hop is the whole reason for the MultiThreadedMessageDispatcher but there is no reason for the last thread switch. If you work on SNMP4J threading in the future, please consider addressing this undesirable side-effect. _______________________________________________ SNMP4J mailing list [email protected] http://lists.agentpp.org/mailman/listinfo/snmp4j
