Warren, You can (and should) handle such a situation in your code by implementing a TransportStateListener and add it to your TcpTransportMapping.
I have no idea how this could be solved in a generic way without a negative impact on existing code. Any suggestions are welcome. Regards, Frank On 28.12.2009 15:57, Warren Cooper wrote: > If there is a connection problem between an SNMP agent configured to > send TCP in its attempt to send events to an SNMP server, and there is > a problem making a connection, many attempts to send the events will > fail. ( It's a problem because the pending list (member in > DefaultTCPTransportMapping) will continue to grow. > > To see the problem, configure an SNMP client to send 40 events over TCP > to a SNMP server expecting UDP. > (But this problem would happen in any case where if > (entry.getSocket().isConnected()) ) check in processPending() is not true. > As you know, this is a serious problem since CPU resources are impacted > and memory could eventually be exhausted if the problem continues for > over an extended period of time and enough events are written to the > 'pending' list object instance. > > thanks > _______________________________________________ > 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
