Preventive Service Planning
Abstract
If no redelivery delay override setting is set in a WebLogic environment for the continuous queue, performance can be severely degraded and log files can fill up with repeated error messages about that transaction.
Content
If the Redelivery Delay Override setting for the continuous queue in WebLogic is not set, performance will be severely degraded. Additionally, the maximo.log can grow very quickly.
When a transaction inbound on the continuous queue has an error, the functionality of Maximo by default is to retry that transaction over and over again until manual intervention occurs either by manually placing the error xml file in the retry folder of the MEA global directory once corrected, or the delete folder to remove it from the queue permanently. However, if the redelivery delay override setting in the WebLogic console is not set, this retry function will occur instantaneously over and over again, leading to performance degradation, and possibly filling up the maximo.log in a short period of time which can cause this log to grow so large that you can run out of disk space.
It is recommended that the redelivery override setting be set to no less than 30 seconds. This means that each error transaction in the queue once rejected by Maximo for various reasons will only be retried once every 30 seconds, or greater, depending on the value set as the redelivery delay override.
To set this value, perform the following steps:
1. launch the WebLogic console and navigate to services/jms/servers/mxintcqinserver/destinations/mxintcqin
2. click on the redelivery tab
3. In the Redelivery Delay Override field, enter a value that represents the number of milliseconds that you would like to delay any error transactions in the continuous queue before being redelivered.
e.g. 30000 is 30 seconds
4. Apply the changes and restart the WebLogic application server.
Was this topic helpful?
Document Information
Modified date:
13 April 2021
UID
swg21293669