Skip to main content

Websphere MQ – inetd or init script

Was implementing an MQ cluster at work recently, and the question arose on setting up init scripts for MQ, specifically the listener, runmqlsr. I was advised that inetd is the usual method for setting up any MQ daemon.

However, I read a blog post on A Hursley view on MQ blog, and it stated that launching the runmqlsr seperately, and not using inetd is the now preferred method of having your MQ daemon running.

They point to an IBM FAQ that says since MQ V5.3, using inetd (amqcrsta) is a “… massively unthreaded approach” to having MQ listen for messages.

In our Load testing, we have not used inetd (pointing to amqcrsta) as the listener, but runmqlsr.
We have decided to continue this into production as changing this may invalidate our load testing results.

I will be, on Solaris 9, setting up a SYSV init script setup for the MQ runmqlsr script we already use. A happy me, and a happy MQ server.