Impacts when RabbitMQ service is down
When the RabbitMQ goes down, some of the operations are no longer allowed to be performed, whereas the others go on hold and are resumed after the RabbitMQ is up and running again.
Here is the list of operations that are resumed after the RabbitMQ comes up.
| S. No. | Operation (When...) |
|---|---|
| 1 | Refreshing the connection pool for a DB Info account. |
| 2 | Updating any property in Settings. |
| 3 | Activating a Kafka Listener. |
| 4 | Deactivating a Kafka Listener. |
| 5 | Activating a non-transactional ASB Listener. |
| 6 | Dectivating a non-transactional ASB Listener. |
| 7 | Activating a non-transactional JMS Listener. |
| 8 | Deactivating a non-transactional JMS Listener. |
| 9 | Any caching operation is performed for any action on the GUI. |
| 10 | The application sends out automated email notification regarding password expiration. |
| 11 | Importing or Deleting a certificate from Settings > Certificates. |
| 12 | The application deactivates an event due to JMS server unavailability. |
| 13 | The application performs cleanup of logs and archived logs. |
| 14 | Adding a Mapping to the AIMap library from Mapping > More > Add to AIMap. |