| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| messages stuck in CONFIG.REPLY after 2-3 deploys |
« View previous topic :: View next topic » |
| Author |
Message
|
| piyalida |
 Posted: Sun Mar 12, 2006 6:19 am Post subject: messages stuck in CONFIG.REPLY after 2-3 deploys |
 |
|
Novice
Joined: 21 Oct 2002
Posts: 22
Location: New York
|
Hi,
I've WMB components all installed on Windows.Message Broker Toolkit is version 6.0.After 2-3 deploys to the broker from the toolkit,I don't get responses from configmgr for subsequent deploys.I see messages stuck up in SYSTEM.BROKER.CONFIG.REPLY queue.No errors in MQClientJava tracing,CMP tracing,event viewer.
Broker,Configmgr share the same qmgr.
Any clues???
Thanks |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Sun Mar 12, 2006 6:54 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Looks like a broken Config Manager; is it running - i.e. can you start new connections to it from the toolkit?
Check the system log for errors (if you haven't already; I assume by 'event viewer' you mean the CM's event log).
EDIT: Actually, scratch that, I'm getting my queues mixed up. The SYSTEM.BROKER.CONFIG.REPLY queue is used by the CMP for receiving messages from the CM. If a toolkit (or any another CMP application) dies unexpectedly, any messages for it will be left on this queue. This is fine - these messages expire after a short while (10 minutes, I think) and eventually the Config Manager will realise the application has gone away and not send it any more stuff. But this means that the queue can temporarily contain messages that will never be picked up - this is all as designed.
The fact that subsequent deploys aren't working may well be unrelated; what error message are you getting?
-Matt |
|
| Back to top |
|
|
| piyalida |
| Posted: Sun Mar 12, 2006 2:48 pm Post subject: |
|
|
Novice
Joined: 21 Oct 2002
Posts: 22
Location: New York
|
Hi Matt,
You are right.The message broker toolkit stops responding after then.I need to forcefully kill the toolkit process.MQJavaClient trace does not show anything abnormal.There are no errors in the CMP trace either.What other traces I can look at to determine the cause of MB toolkit abruptly failing.Yes,I was referring to system log for Configmgr when referring to event viewer.
Thanks |
|
| Back to top |
|
|
| wschutz |
| Posted: Sun Mar 12, 2006 2:51 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Mar 13, 2006 3:19 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Agreed with wschutz - try installing FP01 for the toolkit.
You might also like to try connecting and deploying using the CMP API Exerciser (installed with the runtime package). That will indicate whether it is the toolkit environment that's specifically hanging, or whether it's something lower level.
Either way, if FP01 doesn't sort the problem, please raise a PMR.
Regards
-Matt |
|
| 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
|
|
|
|
