How do I view and manage message queues?

To view messages retained in a message queue

To set the number of retries for EMS message queues

To set how often the message queue attempts to send a retained message

If you have configured event and incident forwarding through queues to third party software integrations, you can view the event and incident messages that have been sent through the queue from the EventForwardQueue.log located in entuity_home\log directory.

The EventForwardQueue.log message log lists the messages that have been sent, are being retained in a message queue, and while retained, the retries count for each message increases. When a message is consumed from a message queue and successfully reaches its endpoint, the log shows the message as acknowledged and cleared from the message queue. 

Please see this article for more information on EMS Actions. 

To view messages retained in a message queue:

1. Navigate to the entuity_home\log directory and open the EventForwardQueue.log file.

2. Review the message log entries. For example:
    

   04/29/2026 17:07:15 INFO  com.entuity.eventsengine.EventForwardQueue - Splunk_default: new message queued, message count = 3
   04/29/2026 17:07:15 INFO  com.entuity.eventsengine.EventForwardQueue - Splunk_default: accepting event: e48, action: null, data: {"event":{"source":{"ref":"Entuity EntuityServer","name":"Power Supply 1 on ProLiant","type":"Hw Power Supply"},"title":"Component Error on Power Supply 1 on ProLiant","message":"Error State  : Power Supply 1:\nModel: 865414-B21\nFirmware: 1.00\nPN: 866730-001\nin Model: ProLiant DL380 Gen10","callback_url":"https://10.0.0.0/webUI/main.do?url=/webUI/objectSummary.do%3Fserver%3Dxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx%26id%3D1773","properties":{"swId":1773,"id":48},"severity":"Severe","eventClass":"ENTUITY.EVENT"}}
   04/29/2026 17:07:15 INFO  com.entuity.eventsengine.EventForwardQueue - Splunk_default: consuming message ID 2d825ef9-25d3-4c05-88ed-0d72f866e959, TIME=1777496835
   04/29/2026 17:07:15 INFO  com.entuity.eventsengine.EventForwardQueue - Splunk_default: removed message ID from queue 2d825ef9-25d3-4c05-88ed-0d72f866e959, TIME: 1777496835
   04/29/2026 17:07:15 INFO  com.entuity.eventsengine.EventForwardQueue - Splunk_default: retries for message 2d825ef9-25d3-4c05-88ed-0d72f866e959 = 1
   04/29/2026 17:07:15 INFO  com.entuity.eventsengine.EventForwardQueue - Splunk_default: message ID 2d825ef9-25d3-4c05-88ed-0d72f866e959 is acknowledged and cleared

    

To set the number of retries for EMS message queues:

1. Open the event-engine-cfg-template.properties file, located in the entuity_home\etc directory.

2. Edit the number of message queue retries that EMS can attempt. The default number of retries is 5.
    

   messageQueueRetries = 5
   

    

3. Save the event-engine-cfg-template.properties file, and then restart the eventEngine process which can be done by either stopping and starting Entuity, or using the following command at the entuity_home/bin directory:
    

   ./stop eventEngine

    

To set how often a message queue attempts to send a retained message:

1. Open the startup_xxxx.cfg file, located in the entuity_home/etc directory.

2. In the eventEngine section of the file, edit the  = -DrecoverSessionScheduledPeriodSec=300 line to update the frequency, in seconds, at which the message queue sends its retained messages to any listening consumers. The default value is 300 seconds.
    

   [eventEngine]
   state=normal,nolicense
   capabilities=polling
   type=command
   start=${install.JAVA}
     = -server -Xrs ${eventEngine.jvmArgs}
     = -Djdk.xml.entityExpansionLimit=0
     = -Dentuity.cfg.dir=${ENTUITY_HOME}/etc
     = -Dlog4j2.configurationFile=file:/${ENTUITY_HOME}/etc/event-engine-log4j2.properties
     = -Dsn.cfg=${ENTUITY_HOME}${FPS}etc${FPS}sn.cfg
     = -Dmoog.cfg=${ENTUITY_HOME}${FPS}etc${FPS}Moogsoft.cfg
     = -Dsplunk.cfg=${ENTUITY_HOME}${FPS}etc${FPS}Splunk.cfg
     = -Dslack.cfg=${ENTUITY_HOME}${FPS}etc${FPS}Slack.cfg
     = -Dhelix.cfg=${ENTUITY_HOME}${FPS}etc${FPS}Helix.cfg
     = -Djava.rmi.server.hostname=127.0.0.1
     = -DrecoverSessionScheduledPeriodSec=300
    

    

3. Save the startup_xxxx.cfg file, and then restart the eventEngine process which can be done by either stopping and starting Entuity, or using the following command at the entuity_home/bin directory:
    

   ./stop eventEngine