[SNMP4J] Problem with Snmp.removeNotificationListener

Frank Fock fock at agentpp.com
Mon Feb 12 18:53:19 CET 2007


Hi Nídia,

If I understand you right then you want to
dynamically control trap receiving ports (addresses).
Then you should use the default constructor of
Snmp() to create your instance.

Using that, you will not have any "initialization"
transport mapping.

Does this help?

Best regards,
Frank

Nídia S. Campos wrote:
> Hi!
> I've configured  my manager to listen UDP and TCP traps using
> Snmp.addNotificationListener(), and,  Snmp.removeNotificationListener() 
> with
> respectives addresses to change port addresses.
> Debugging, I notice that it doesn't work to DefaultUdpTransportMapping port
> trap that the manager is initialized with, then a new thread is created and
> the older isn't killed. If I change the port again, it works but the one of
> initialization remains....
> To DefaultTcpTransportMapping, it works but 
> Snmp.removeNotificationListener()
> returns false.
> 
> So, anyone may help me?
> 

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com




More information about the SNMP4J mailing list