[SNMP4J] MultiThreadedMessageDispatcher

[Frank Fock]

The recommended way is using a WorkerPool for AgentConfigManager
(which is then used by the CommandProcessor) only. As you correctly
pointed out, there is no benefit in using the MultiThreadedMessageDispatcher
instead the MessageDispatherImpl for an agent using the CommandProcessor
class.

Am 15.01.2010 15:36, schrieb Clement_Pellerin at ibi.com:
> 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
> SNMP4J at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/snmp4j
>