Dan - There is a good solution to this problem if your applications are connecting as clients, then if you give each application its own server/client channel pair and monitor the status, you can see who is abusing the resources.
If your applications are connecting in bind mode, I cant think of a good way to do it unless you know great deal about shared memory and can monitor how many SHMEM attachments to MQSeries your applications make. The other simplest solution would be to run one application at a time in a mirrored environment and find out who is the bad guy. Michael. ----- Original Message ----- From: "Wood, Dan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, December 18, 2002 12:01 Subject: AMQZLAA0.EXE > We have an MQ application running on Win2k using MQ v5.2.1. This server > would occasionally crash on us, so we started to monitor the tasks that were > running. On a daily basis the number of amqzlaa0 tasks increase, and within > a couple of weeks of running(without a reboot) the number of these tasks is > 100+. Now, I'm inclined to think that this is a misbehaving application(not > disconnecting properly), but before I accuse the application folks, I > thought I see if anyone else might have run in to this issue or have some > suggestions. > Thanks, for any input. > > Dan L Wood > AIT - Technical Services > [EMAIL PROTECTED] > 319-896-6985 > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
