MQ listeners operations depend on whether Pega Platform is deployed as an Enterprise application (EAR file) or a Web application (WAR file). See PDN article Using MQ and JMS Services with Enterprise Application deployment.
Three settings affect how MQ listener requestors run. They control whether the listeners can run, when the listeners start, and where the listeners can run:
initServices/initMQ
entry in the prconfig.xml file or Dynamic System Settings. (enabled by default)The Blocked check box on the Properties tab determines whether the listener requestors defined by this MQ Listener data instance start. If this check box is cleared, these listeners start when Pega Platform starts (on eligible nodes). You can also stop and restart them using the Listener Management menu in the System Management application.
If the Blocked check box is selected, they do not start when a Pega Platform node starts and you cannot start them in the System Management Application until you clear the Blocked option and save the listener instance.
The prconfig.xml file or Dynamic System Settings control when MQ listeners start. To cause unblocked MQ listeners to start when Pega Platform starts, edit this file to add or update the initServices/initMQ
setting:
<env name="initServices/initMQ" value="true"/>
If this entry is not present in the file, or the value is not set to "true","y" or "yes", you can start unblocked MQ listeners only from System Management Application.
The options listed in the Start Option property on the on the Properties tab determine where the listener starts. The following options are available.
Run on all nodes
— The listener is run on all nodes for all servers in a cluster.Node based startup
— The listener is started only on specified nodes.Host based startup
— The listener is started on a specified number of nodes on specific servers within the cluster.Use the remote logging feature to debug MQ listeners: