|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQ- Fast response and slow response intermittent |
« View previous topic :: View next topic » |
Author |
Message
|
idhayham |
Posted: Fri Mar 20, 2009 11:02 pm Post subject: MQ- Fast response and slow response intermittent |
|
|
Novice
Joined: 29 Jan 2009 Posts: 11
|
My system uses MQseries through which orders flows. I am experiencing slow orders in between.I thought it could be any errors with orders.But the same orders went fast when i issued the orders again. I am believing the process trigger is experiencing some problem. We had a release 2 weeks before one of our upstream system had a server rehost. From that it had a problem of slow orders. please help me.
I am attaching the Queuecluster parameters with this.
QUEUE(QC.CLIENT) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2007-11-27)
ALTTIME(10.32.35) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER(PROD) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2007-05-29) CRTIME(09.50.39)
CURDEPTH(10) DEFBIND(NOTFIXED)
DEFPRTY(0) DEFPSIST(YES)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR(This queue is for CLIENT requests)
DISTL(NO) GET(ENABLED)
NOHARDENBO
INITQ(SYSTEM.DEFAULT.INITIATION.QUEUE)
IPPROCS(1) MAXDEPTH(5000)
MAXMSGL(1048576) MONQ(QMGR)
MSGDLVSQ(FIFO) TRIGGER
NPMCLASS(NORMAL) OPPROCS(1)
PROCESS(QP.CLIENT.REQUEST) PUT(ENABLED)
QDEPTHHI(80) QDEPTHLO(20)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QDPMAXEV(ENABLED) QSVCIEV(NONE)
QSVCINT(999999999) RETINTVL(999999999)
SCOPE(QMGR) SHARE
STATQ(QMGR) TRIGDATA( )
TRIGDPTH(1) TRIGMPRI(0)
TRIGTYPE(FIRST) USAGE(NORMAL) |
|
Back to top |
|
 |
Vitor |
Posted: Fri Mar 20, 2009 11:33 pm Post subject: Re: MQ- Fast response and slow response intermittent |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
idhayham wrote: |
please help me. |
How? There's no detail here.
Do you mean "slow" orders in the sense they took longer than SLA to arrive on their target queue? Or that they sat on the target queue for longer than SLA before being processed? How long is the SLA? What is the topology?
More specifically, why are you posting the definition of a cluster queue if you suspect a probem with triggering? A trigger works locally on a givne cluster queue instance. In the example you've given, the trigger's probably worked fine as it's trigger first & there's a process been triggered. Not an especially fast process it seems, but there is one and WMQ's involvement in it directly will have ended.
Bit more detail on your problem needed really. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
bruce2359 |
Posted: Sat Mar 21, 2009 5:16 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
A few places to begin doing performance analysis:
Is this the only instance of the queue QC.CLIENT in cluster PROD?
Are the slow downs occuring at the same time each day?
Any new applications running on the server?
Is the server hardware experiencing high CPU utilization or high disk i/o at the times of the slowdown?
Is the network experiencing error at these times?
You might begin by capturing some queue and channel monitoring statistics. Refer to the WMQ Monitoring manual. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|