SQL Server

Finalize Thread Pool on Program Exit

See more Async Examples

If your code is calling asynchronous Chilkat methods (i.e. methods having names ending with "Async"), then it's a good idea to call the FinalizeThreadPool when your program is about to exit. It's best if all asynch methods have cleanly finished prior to calling FinalizeThreadPool. If any asynchronous methods are in progress when FinalizeThreadPool is called, they will be aborted and the threads shutdown. SQL Server

--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    --  Asynchronous Chilkat methods are run in background threads managed
    --  by a thread pool manager thread, which is also a background thread.
    --  Prior to exiting, it is good practice to ensure all asynchronous methods
    --  have completed or are aborted/cancelled, and that the thread pool manager
    --  thread is also shutdown.  
    --  
    --  The FinalizeThreadPool method should be called just before the application exits
    --  to ensure all background threads, including the thread pool manager thread, are
    --  cleanly shutdown.

    --  This is how to do it:
    DECLARE @glob int
    EXEC @hr = sp_OACreate 'Chilkat.Global', @glob OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    DECLARE @success int
    EXEC sp_OAMethod @glob, 'FinalizeThreadPool', @success OUT

    EXEC @hr = sp_OADestroy @glob


END
GO