|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Health Checking the QM in a Unix Cluster |
« View previous topic :: View next topic » |
Author |
Message
|
PeterPotkay |
Posted: Wed Sep 24, 2008 11:34 am Post subject: Health Checking the QM in a Unix Cluster |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Looking at the Broker health check script for Linux H.A. in the IC91 Support Pack, it does the following to determine if the QM is up:
Code: |
# ------------------------------------------------------------------
# Check that the queue manager is running or starting.
#
su - $MQUSER -c "echo ping qmgr | runmqsc ${QM}" > /dev/null 2>&1
pingresult=$?
# pingresult will be 0 on success; non-zero on error (man runmqsc)
if [ $pingresult -eq 0 ]
then
# ping succeeded - Queue Manager is responsive"
STATE="started"
else
# ping failed
# Don't condemn the QM immediately, it may be in startup.
# The following regexp includes a space and a tab, so use tab-friendly
# editors.
srchstr=" $QM[ ]*$"
cnt=`ps -ef | grep strmqm | grep "$srchstr" | grep -v grep \
| awk '{print $2}' | wc -l`
if [ $cnt -gt 0 ]
then
# It appears that QM is still starting up, tolerate
STATE="starting"
else
# There is no sign of QM start process
STATE="stopped"
fi
Fi |
Is a PING in runmqsc enough? Does anyone do anything more? I'm thinking what if the MQ Listener goes down, for example. For a QM that hosts hundreds of MQ Clients a QM without a listener is not much good. But then again, the listener is only needed for new connections. If the listener dies, is it worth failing over and knocking out all the existing connections? Or is PING QMGR robust enough?
Is anyone privy to what the Windows MQ health check is doing internally in a MSCS cluster? IBM released that as part of the core product, so I wonder how in depth it gets with checking the health of the QM. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
gbaddeley |
Posted: Wed Sep 24, 2008 9:04 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
I wonder why the script doesn't just grep the output of dspmq. Maybe it predates the existence of that command. The MQ listener is a separate process in MQ, so it would need to be checked separately. _________________ Glenn |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Sep 25, 2008 6:17 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Clearly, the script is not comprehensive. It's a sample.
A comprehensive health checker script for a specific qmgr would include checking all of the things that the qmgr must have to satisfy the business applications, like: the status of channels, listeners, availability of application queues (put/get enabled, trigger attributes), existence of processes, namelists, trigger monitor, applications, ...
As configuration changes take place, the script would need to be updated to include these new/changed things. _________________ 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
|
|
|
|