Failure in the listener port

  If a listener port should fail to start, or lose its connections to the queue manager then it is possible to make it retry. There are two settings at the message listener service that govern how many times (re)starting a listener port should be attempted and how long the interval should be in between.

These two settings are:

  1. MAX.RECOVERY.RETRIES

    Use this to specify the number of attempts to start the listener port. The default for this setting is 5 attempts.

  2. RECOVERY.RETRY.INTERVAL

    This setting sets the time interval between the retries. The default for this value is 60 seconds.

If these settings are not changed then the listener port will attempt to start once every 60 seconds over 5 minutes. If the listener port has been unable to start in this time then it will not be started, unless done manually.

Change these values to provide an adequate amount of retries so that your application can recover. For example, if you are using hardware or operating system level clustering to provide failover, then these settings need to be configured to keep retrying for the period it typically takes for failover to occur. In this way the failure of the queue manager or Embedded JMS server will be masked as a blip in throughput rather than the listener port stopping completely.

Follow these steps to use these two values:

  1. Go to Servers -> Application Servers -> <MyAppServer> -> Message Listener Service -> Custom Properties.

  2. Click the New button.

  3. For name specify either:

    MAX.RECOVERY.RETRIES
    RECOVERY.RETRY.INTERVAL

  4. Enter the value you wish to use, and an optional description. Remember the retry interval is in seconds.

  5. Press OK and save your configuration.

Once completed it will look similar to Figure 15-12.

Figure 15-12 The listener port retry settings

The settings will come into operation the next time the appserver is restarted.

Not that this behavior is slightly different for connections to a message broker. When the JMS provider code attempts a connection to the message broker for publish/subscribe messaging, if there is a problem getting a response from the broker then it will wait for three minutes before timing out. This means that if a listener port is trying to start or restart there will be an additional timeout value added on between retries to the retry interval. This message broker connection timeout is not configurable from within WAS.

 Prev | Next

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.