locked
FwpmEngineClose can hang if a 3rd party app has a transaction in progress RRS feed

  • Question

  • Hi,

    Our process can fail to stop in a timely manner when a 3rd party application has the transaction lock for a long period.  This occurs on FwpmEngineClose0 (our filters are dynamic) even though we have set the txnWaitTimeoutInMSec on the engine session to 10 seconds.  It appears that this timeout doesn't apply to session closing.

    Obviously we could not call FwpmEngineClose0 and just let the app terminate, WFP will then close it anyway.  However in the future we would also like to close and reopen sessions at will, e.g. to support upgrades etc. so is there a better way.  I hope we don't have to perform this on a separate thread just in case it could block.

    Many thanks.

    Monday, July 29, 2013 2:56 PM