APAR status
Closed as program error.
Error description
Environment: WDI 3.2.1 for Windows with CSD27 When running the WDI MQ advanced adapter for long periods, wdiserver.exe accumulates many memory handles and memory usage in wdiserver.exe and wditrigger.exe grows slowly. There is an apparent memory leak and memory handle leak. If left unchecked, an excessive handle count from wdiserver.exe will cause a shortage on the server. Note: Also tried tweaking the wdi.properties waitinterval and numtranslator but with same results. Recreate scenario: - Import maps and profiles. - Start the advanced adapter: wdiserver - Use Windows Task Manager to monitor the handles. - Use RFHUtil to put input XML msg onto XML_IN trigger queue. - Check Handle count and see it has increased by 2. Further analysis shows a leak of 2 handles to occur in wdiserver.exe, but only after wdiservice.exe has stopped servicing the queue. In other words, if wdiserver is emptying a queue of one, or of many messages, there are always two handles leaked. Also note that along with the wdiserver.exe ever increasing handle count, there is also a small memory leak in both wdiserver.exe and wditrigger.exe, which remain active until adpater shutdown. maps_profiles.eif test_392_O_GDU353.xml wdi.properties Keywords: handle handles memory leak slow performance degradation degrade degrades
Local fix
Periodically restart the Adavanced adapter by issuing: wdishutdown followed by wdiserver commands.
Problem summary
WDIServer process retains two additional resource HANDLES on Windows for every WDIService child process that it starts.
Problem conclusion
Added code to free the process and thread handles after the Create.
Temporary fix
Comments
Defect P8011991 in CMVC for WDIServer and WDIServer33. Applies to wdi 3.2 CSD28 and wdi 3.3 SFP2 WDITranslatorProc.cpp (P8011991)
APAR Information
APAR number
PK82145
Reported component name
WEBS DI ZOS
Reported component ID
5655I4003
Reported release
330
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-09
Closed date
2009-03-09
Last modified date
2009-03-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS DI ZOS
Fixed component ID
5655I4003
Applicable component levels
R330 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
22 August 2022