| Author |
Message
|
| hkhan12 |
 Posted: Wed Oct 03, 2007 6:11 pm Post subject: Performance Issue |
 |
|
Voyager
Joined: 08 Aug 2002
Posts: 98
|
Hi there,
I'm facing a performance issue. Message receiving after 3 minutes and some time around 5 minutes.
Here is the environment details:
Sender Application (Seibel) running on AIX 5
Receiving Application (Java) running on Solaris 8
It is inserting messages into a DB after receiving. At this point I do not have information if the receiving application doing a two phase commit.
This is a WMQ cluster environment.
At this point I just want to know the possible reasons that can cause the delay for 3 minutes to receive.
Any input would be highly appreciated.
Thank you, |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Oct 03, 2007 10:53 pm Post subject: Re: Performance Issue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hkhan12 wrote: |
At this point I just want to know the possible reasons that can cause the delay for 3 minutes to receive.
|
- Seibel heavily loaded and running slow
- Java heavily loaded and running slow
- Database heavily loaded and running slow
- Database badly designed and deadlocking
- Database badly structured and inserts causing page faults (or whatever the term is for this db)
- Some other bizzare db problem
- Network delay across cluster
- Queue manager heavily loaded and running slow (unlikely in a cluster I'd have thought - they'd all have to be running equally slow!)
These would be my first guesses at problem areas. Though in truth my first move would probably be to investigate where this 3 minutes is being spent rather than guess.
_________________
Honesty is the best policy.
Insanity is the best defence.
Last edited by Vitor on Wed Oct 03, 2007 11:50 pm; edited 1 time in total |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Oct 03, 2007 11:36 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Test it in parts, send the message to a local queue first, then a remote queue (which is not being processed).
See where the delay is occuring. It's not likely to be MQ. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Oct 04, 2007 3:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
clock on DB server 4 minutes different than clock on Seibel server...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Oct 04, 2007 5:30 am Post subject: |
|
|
Guest
|
Start with baisc questions:
-has this application always been a slow performer?
-has it recently begun to be slow performer?
-has it been gradually become slower over time?
-are other applications also experiencing slowdowns?
-what has changed? (this is IT! Lots of things change) new applications? more applications? new users? more transactions? new hardware? new software? new configuration?
The usual sources of poor performance include: bad database design, bad sql calls, poorly defined/no indices, and poorly written applications, JAVA. |
|
| Back to top |
|
|
| hkhan12 |
| Posted: Sat Oct 06, 2007 5:44 am Post subject: |
|
|
Voyager
Joined: 08 Aug 2002
Posts: 98
|
Hi Everybody,
Thank you so much for all your inputs. Today I found that more than 35 amqzlaa0 processes are running on the message receiving server where the application taking 3 minutes to receive the message.
Do you guys think that these processess are causing this issue. I beleive so.
If I want to kill these processes, currently connected application will also loose connection to Queue Manager. How would I know the old and current connections?
The processess are as follows:
mqm 15176 2808 0 Sep 15 ? 68:01 amqzlaa0 -mEESO461P -fip124
mqm 1058 2808 0 Sep 07 ? 147:01 amqzlaa0 -mEESO461P -fip88
mqm 29936 2808 0 Sep 07 ? 117:46 amqzlaa0 -mEESO461P -fip87
mqm 29631 2808 0 Sep 07 ? 277:02 amqzlaa0 -mEESO461P -fip86
mqm 6118 2808 0 Sep 07 ? 127:25 amqzlaa0 -mEESO461P -fip96
mqm 5878 2808 0 Sep 07 ? 113:39 amqzlaa0 -mEESO461P -fip95
mqm 13917 2808 0 Sep 16 ? 71:12 amqzlaa0 -mEESO461P -fip125
mqm 6435 2808 0 Sep 07 ? 67:16 amqzlaa0 -mEESO461P -fip97
mqm 28303 2808 8 Jul 31 ? 2926:28 amqzlaa0 -mEESO461P -fip42
mqm 6729 2808 0 Sep 07 ? 21:35 amqzlaa0 -mEESO461P -fip100
mqm 17587 2808 0 Sep 16 ? 8:28 amqzlaa0 -mEESO461P -fip126
mqm 28765 2808 0 Sep 07 ? 510:40 amqzlaa0 -mEESO461P -fip84
mqm 12153 2808 0 Sep 25 ? 29:00 amqzlaa0 -mEESO461P -fip127
mqm 6668 2808 0 Sep 07 ? 155:53 amqzlaa0 -mEESO461P -fip99
mqm 5615 2808 0 Sep 07 ? 136:48 amqzlaa0 -mEESO461P -fip94
mqm 10991 2808 0 Sep 14 ? 21:30 amqzlaa0 -mEESO461P -fip123
mqm 7301 7285 0 16:32:54 pts/1 0:00 grep amqzlaa0
mqm 27678 2808 0 Sep 07 ? 8:06 amqzlaa0 -mEESO461P -fip101
mqm 4586 2808 0 Sep 10 ? 59:05 amqzlaa0 -mEESO461P -fip108
mqm 6598 2808 0 Sep 07 ? 45:44 amqzlaa0 -mEESO461P -fip98
mqm 5248 2808 0 Sep 07 ? 210:13 amqzlaa0 -mEESO461P -fip93
mqm 4719 2808 0 Sep 10 ? 130:49 amqzlaa0 -mEESO461P -fip109
mqm 29315 2808 0 Sep 07 ? 72:12 amqzlaa0 -mEESO461P -fip85
mqm 1375 2808 0 Sep 07 ? 18:46 amqzlaa0 -mEESO461P -fip107
mqm 3559 2808 0 Sep 07 ? 60:21 amqzlaa0 -mEESO461P -fip92
mqm 10957 2808 0 Sep 14 ? 133:04 amqzlaa0 -mEESO461P -fip122
mqm 4028 2808 0 Jul 30 ? 94:59 amqzlaa0 -mEESO461P -fip36
mqm 12504 2808 0 Sep 25 ? 35:42 amqzlaa0 -mEESO461P -fip128
mqm 28426 2808 0 Sep 07 ? 172:44 amqzlaa0 -mEESO461P -fip78
mqm 2816 2808 0 Jul 30 ? 646:24 amqzlaa0 -mEESO461P -fip0
mqm 3493 2808 0 Sep 07 ? 195:28 amqzlaa0 -mEESO461P -fip91
mqm 22107 2808 0 Sep 13 ? 8:13 amqzlaa0 -mEESO461P -fip110
mqm 1608 2808 0 Sep 07 ? 655:25 amqzlaa0 -mEESO461P -fip89
mqm 9635 2808 0 Sep 14 ? 22:27 amqzlaa0 -mEESO461P -fip117
mqm 3337 2808 0 Jul 30 ? 2012:03 amqzlaa0 -mEESO461P -fip13
mqm 22108 2808 0 Sep 13 ? 158:21 amqzlaa0 -mEESO461P -fip111 |
|
| Back to top |
|
|
|
|
