Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/169052

From BetaArchive Wiki
Knowledge Base


PRB: Memory Leak in Custom Order Processing Pipeline Components

PSS ID Number: 169052

Article Last Modified on 8/27/1999



The information in this article applies to:

  • Microsoft Merchant Server 1.0



This article was previously published under Q169052

SYMPTOMS

When a custom component is used in the order processing pipeline (OPP), there is a memory leak of 4 - 40 KB for each execution of the pipeline. The OPP is processed when one of the order.additem, order.plan, and order.purchase actions is run. The number of stages processed varies for each of these actions. For more information, please refer to the "Order Processing Components" chapter in the product documentation.

Depending on the shopper traffic at your site, the Windows NT Server computer that is running Merchant Server 1.0 store processes may eventually run out of virtual memory.

WORKAROUND

To work around this problem, do either of the following:

  • The leak occurs because of a problem in MerchExt.dll. This problem has been addressed in a hotfix, and you can obtain a newer MerchExt.dll file by contacting Microsoft Technical Support. Note that the memory leak only occurs when you have a custom component (written using the OPP API) plugged into the OPP. You do not need this hotfix if there are no custom components, written either by you or a third party, in the OPP. The default, optional, and required OPP components that come with the Merchant Server 1.0 system do not have this problem.

    -or-

  • Upgrade to Microsoft Commerce Server 2.0. For more information, see the Web site at:


Keywords: kbprb KB169052
Technology: kbAudDeveloper kbMerchServ100 kbMerchServSearch