TopoActionListener never gets notified on MO deletion

in WebNMS Framework • 10 years ago

Hi,

I created a Topo listener and it is running on FE server as a separate thread. Update method is invoked on events like addition or update but never on MO deletion. MOs are deleted exclusively using TopoAPI methods:

deleteObjectAndSubElements(String objKey);
deleteObject(ManagedObject obj, boolean deleteSubElements, boolean dealWithLocks);

the class itself:

public class TopoListner implements TopoActionListener, RunProcessInterface

{

private boolean isInitialized = false;

@Override

public void callMain(String[] args)

{

TopoAPI topo = (TopoAPI) NmsUtil.getAPI("TopoAPI");

try

{

topo.register(this);

}

catch (Exception e)

{

Log.exception("Couldn't create TopoListener process, topo.register() failed ", e);

return;

}

isInitialized = true;

}

@Override

public void update(TopoNotificationEvent event) throws RemoteException

{

String eventType = event.getUpdateType();

Log.debug("=== TopoListener === eventType is [" + eventType + "]");

}

@Override

public boolean isInitialized()

{

return isInitialized;

}

@Override

public void shutDown()

{

// Nothing to do on shutdown

}

Am I doing something wrong or is this a bug? Considering it a bug, is there a workaround?

Regards,

Tom

Replies(2)

ayush

Re: TopoActionListener never gets notified on MO deletion

10 years ago

Hi Tom,

When you use the method deleteObjectAndSubElements(), you need to add TopoBulkListener to get notified, as mentioned in below link

deleteObjectAndSubElement()

Where as with the method deleteObject(ManagedObject obj, boolean, boolean), should get you the notification. Could you please try with this method. You can enable the log level for TOPOERR and TOPOUSER in log4j.xml, so that you can see the listener which are been called in logs file.

Thanks,

Ayush

tomaszaor..

Re: TopoActionListener never gets notified on MO deletion

10 years ago

Hi Ayush,

looking back in the code I realized that only deleteObjectAndSubElements() is called in my case, therefore adding a TopoBulkListener solved my problem. Thanks a lot ;)

Have a nice day,

Tom

Top Reply

Response title

Attachments

New to this Portal?