keith_k

Custom Perl probe unregisters port at hub restart

Discussion created by keith_k on Nov 4, 2009
Latest reply on Nov 6, 2009 by keith_k
I have a custom probe named collect_data, and it attaches to a queue on our hub.  Whenever the hub restarts, the controller on the host running the probe issues this alarm:

Port unregister from active probe collect_data

The probe continues to run fine and still gets messages from the hub queue.  However, it seems to stop listening on the TCP port.  I am actually not 100% sure that it stops listening on the port, but the port is no longer listed in the Infrastructure Manager.  Therefore, I cannot send callbacks requests to it any longer.

Does anyone know why this happens or if I can do something in my Perl code to catch this issue and do something about it?

Thanks,
Keith

Outcomes