| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Is Reciever up and running? |
« View previous topic :: View next topic » |
| Author |
Message
|
| dilse |
 Posted: Fri Aug 13, 2004 5:27 am Post subject: Is Reciever up and running? |
 |
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Guys,
Everytime I want to send some messages to the reciever, I want to know whether MQ on the reciever is up and running or not. What are the different ways that we can find whether MQ on the reciever is up and running? We are using Candle as a monitoring tool, MQ 5.3(Windows200) with CSD07 and MQ5.2(AS/400) with CSD05.
I can think of running an application on the reciever that sends back the status of the reciever frequently(i.e, pinging). and also putting some alerts on the sender to inform whether the reciever is up or not.
Other than these, what are the other ways that we can inquire about whether the reciever is up and running or not?
any suggestion is appreciated...
Thanks..
_________________
DilSe..
Take life as it comes.. |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Aug 13, 2004 6:30 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| From an application point of view you can use COA and COD |
|
| Back to top |
|
|
| dilse |
| Posted: Fri Aug 13, 2004 9:06 am Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Thanks vennela...I will try with that..
_________________
DilSe..
Take life as it comes.. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Aug 15, 2004 12:06 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
From a monitoring point of view I would want following to be checked:
Assumptions:
All your important messages are persistent. If a message is not persistent, there is no need to worry whether it makes it to destination or not.
Check for a listener down:
a) no client conn. == will be noticed and reported by connecting client
b) No comm. between qmgrs == see below
Use monitoring tool for:
Transmission queue depth > 0 and channel status <> running
Channel status retrying
Channel status stopped
Channel status neither stopped nor retrying nor running nor inactive.
This should alert you to something not ok on the transmission front.
Now you could just as well add a 75% full qdepth event for a transmission queue. This would cover the sending being much faster than the receiving.
Normally it would be a bandwidth problem.
Enjoy
 |
|
| 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
|
|
|
|
