Troubleshooting › Message Queue 4.1 Broker Does Not Respond to Scans

Previous Topic: Message Queue 4.1 Broker Stops Immediately After Starting

Next Topic: In HTTPS, Unable to View Invoice in CSV Format from Invoice History UI

Message Queue 4.1 Broker Does Not Respond to Scans

Symptom:

In some cases, Message Queue 4.1 Broker fails to respond when I scan the computer on which it is installed for security or port data.

Solution:

The cause could be that Message Queue 4.1 Broker is using dynamic ports (its default setting).

To help enable Message Queue 4.1 Broker to repond to scans, configure it to bind to static ports and IP addresses.

To Configure Message Queue 4.1 Broker to bind to static ports and IP addresses

  1. Using the Windows Control Panel, stop the Windows service named MessageQueue 4.1 Broker.
  2. Open the Message Queue 4.1 Broker configuration file named default.properties for editing.

    The default location of this file is C:\Program Files\CA\SC\MessageQueue\4.1\mq\lib\props\broker.

  3. Search for the following string and change the current value (likely 0) to 2202:

    imq.jms.tcp.port=

  4. Search for the following string:

    imq.jms.tcp.hostname=

    Do the following, if they are not already done:

  5. Search for the following string and change the current value (likely 0) to 2203:

    imq.admin.tcp.port=

  6. Search for the following string:

    imq.admin.threadpool_model=dedicated

    Add a new line underneath it and enter the following string:

    imq.admin.tcp.hostname=127.0.0.1

    Note: This value (127.0.0.1) specifies the loopback address, which is accessible only by the computer on which the Message Queue 4.1 Broker is installed.

  7. Search for the following string:

    imq.portmapper.hostname=

    Do the following, if they are not already done:

  8. Save the file.
  9. Start the MessageQueue 4.1 Broker service.

You have configured Message Queue 4.1 Broker to respond to port and security scans.