Don,
This is what I found on IBMLink:
APAR Identifier ...... IC37610 Last Changed ........ 04/02/12
MEMORY AND THREAD HANDLE LEAK WHEN MQM.DLL IS REPEATEDLY
RELOADED (INCLUDING COM+/MTS)
Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 3 Date Closed ......... 03/10/31
Component .......... 5639B4300 Duplicate of ........
Reported Release ......... 520 Fixed Release ............ 999
Component Name MQS V5 FOR WIN Special Notice
Current Target Date ..04/01/02 Flags
SCP ................... NT
Platform ............ WIN/NT
Status Detail: Not Available
PE PTF List:
PTF List:
Release 520 : PTF not available yet
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
Customers COM+ application is involved in a transaction and the
msdtc repeatedly invokes mqm calls. However, inbetween each, mqm
is freed. The mqm library and its dependencies, amqxcs2,
amqmtmgr and amqzst were not designed to be loaded/unloaded in a
long running process and leak storage over time.
.
Repeatedly loading and unloading mqm.dll shows a thread handle
and memory leak. Since this appears to occur under the msdtc,
we need to prevent that from occurring. One cause is the
SuicideThread being terminated forcibly, but other causes exist.
.
LOCAL FIX:
Fix available from 1478.prb (L3 site)
PROBLEM SUMMARY:
Some of the MQ structures are not cleaned up at unload time,
because there is an expectation that the unload occurs as a
result of process termination and hence they will get freed
anyway. Examples are process wide critical sections and the
main control block.
.
However, if the MQ dlls are explicitly involved in a
loadlibray/freelibrary pair, they can therefore appear to show
a memory and handle leak
USERS AFFECTED:
All users of MQSeries 5.2.x and Websphere MQ 5.3 on the Windows
platforms who load and unload MQ libraries explicitly.
PROBLEM CONCLUSION:
This APAR attempts to free all the memory areas and operating
system resources which are created during the intial library
load during DLL_PROCESS_DETACH processing
The fix will be included into:
WebSphere MQ V5.3 CSD06
Windows U200202
AIX U489863
HP-UX U489864
Linux on Intel U489967
Linux on zSeries U489972
Sun Solaris U489865
MQSeries V5.2 CSD09
WINDOWS V5.2.0 U200203
WINDOWS V5.2.1 U200204
AIX U495149
HP-UX V10 U495150
HP-UX V11 U495169
HP-UX V11 DCE U495217
SUN SOLARIS U495167
LINUX U495168
TEMPORARY FIX: NONE
COMMENTS:
MODULES/MACROS: NONE
SRLS: NONE
RTN CODES:
CIRCUMVENTION: NONE
MESSAGE TO SUBMITTER: PTF number updated.
"Thomas, Don"
<[EMAIL PROTECTED]
OM> To
Sent by: MQSeries [EMAIL PROTECTED]
List cc
<[EMAIL PROTECTED]
n.AC.AT> Subject
MS BizTalk Adapter for MQSeries
09/30/2004 02:28
PM
Please respond to
MQSeries List
<[EMAIL PROTECTED]
n.AC.AT>
Group,
We are experiencing a problem between MQ and the Microsoft BizTalk
Adapter. The issue seems to take one of two flavors (or perhaps it's two
different problems), one is the adapter simply crashes and requires a
restart and the other is that the adapter gets corrupted data from the
xmitq
and puts the message on its equivalent of dead letter queue and continues
processing. We have a MS tech rep looking at it and I've opened a PMR with
IBM, but neither is producing much headway. The biggest problem we have is
a
distinct lack of clues. The problem is very sporadic and we can't recreate
it at will, so getting an MQ trace is highly unlikely. About the only info
I
have is a couple of messages in the event log originating form COM+and a
dump the MS guy pulled up for I don't know where. I've attached the dump.
There are no indications of a problem in the MQ error logs. I know this
isn't much but have any of you run into this? Any suggestion would
appreciated.
------------------
Registers & Stack
=============
(89c.1078): Access violation - code c0000005 (!!! second chance !!!)
eax=00000000 ebx=00000000 ecx=01b3ffa4 edx=787454e0 esi=00000000
edi=010e2d80
eip=4e21a74f esp=01b3f72c ebp=010d7c68 iopl=0 nv up ei pl zr na po
nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000
efl=00000246
amqmtmgr+0xa74f:
4e21a74f 8b08 mov ecx,[eax]
ds:0023:00000000=????????
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be
wrong. 010d7c68 42454d51 48505a49 00004255 00000000 amqmtmgr+0xa74f
Module
=====
4e210000 4e243000 amqmtmgr (export symbols) amqmtmgr.dll
Loaded symbol image file: amqmtmgr.dll
Image path: d:\Program Files\MQSeries\bin\amqmtmgr.dll
Image name: amqmtmgr.dll
Timestamp: Tue Jun 17 20:47:19 2003 (3EEFB697)
CheckSum: 0003D14B
ImageSize: 00033000
File version: 5.300.400.3168
Product version: 1.0.0.1
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0809.04b0
CompanyName: IBM Corporation
InternalName: MQM
OriginalFilename: MQM.dll
ProductVersion: 5.3.0
FileVersion: 5,300,0400,03168
PrivateBuild:
SpecialBuild:
FileDescription: MQSeries Thread/MTS Manager
LegalCopyright: Licensed Materials - Property of IBM 5724-B41 (C)
Copyright IBM Corp. 1996, 2002 All Rights Reserved US Government Users
Restricted Rights - Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
LegalTrademarks: IBM is a registered trademark and MQSeries is a
trademark of International Business Machines Corporation
Comments: IBM MQSeries for Windows NT
Don Thomas
MASC - Coraopolis
Phone:+1-412-893-1659
mailto:[EMAIL PROTECTED] <
mailto:[EMAIL PROTECTED]>
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at
http://www.lsoft.comArchive:
http://vm.akh-wien.ac.at/MQSeries.archiveInstructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at
http://www.lsoft.comArchive:
http://vm.akh-wien.ac.at/MQSeries.archive