Open topic with navigation

TIBCO Rendezvous® 8.8.0

# tibrvftMonitor_Destroy()

Function

## Declaration

    tibrv_status tibrvftMonitor_Destroy(
        tibrvftMonitor   monitor);
    tibrv_status tibrvftMonitor_DestroyEx(
        tibrvftMonitor             monitor,
        tibrvftMonitorOnComplete   completionFunction);

## Purpose

Stop monitoring a fault tolerance group, and free associated resources.

Parameter | Description
`monitor` | Destroy this monitor object.
`completionFunction` | Rendezvous software runs this function immediately after all instances of the monitor’s callback function (and internal callback functions) have completed. If callback functions are not running when the monitor is destroyed, the destroy call runs it before returning. If this parameter is `NULL`, `tibrvftMonitor_DestroyEx()` does not run a completion function; instead, its behavior is the same as tibrvftMonitor_Destroy(). See tibrvftMonitorOnComplete.

## Extended Function

Although `tibrvftMonitor_DestroyEx()` prevents future dispatch calls from running the destroyed monitor’s callback function, a callback function might be already running in one or more threads that dispatch events from the same queue. In each thread where the callback function is already in progress, that callback function does continue to run until complete. Rendezvous software ensures that the completion function runs when the last callback-in-progress has completed; for important details, see tibrvftMonitorOnComplete.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Rendezvous®

Copyright © 1997-2025. Cloud Software Group, Inc. All Rights Reserved.