Since RabbitMQ takes care of the indexing tasks, it is worth verifying the status of the RabbitMQ database server to understand the root cause of the problem.
Check if the RabbitMQ message queue, especially indexExistingContent holds more messages despite having no active transactions between Artifactory and Xray. If the message count is more, probably the RabbitMQ server is stuck processing the requests. Perform a stop action against the Xray server and check if the RabbitMQ is still running. netstat -tulpn would reveal if the RabbitMQ is still listening on port 5672.
If the service is still listening on this port, we need to clear the process and perform a restart of the Xray service. This might help us to clear off the stuck messages.
Check if the RabbitMQ message queue, especially indexExistingContent holds more messages despite having no active transactions between Artifactory and Xray. If the message count is more, probably the RabbitMQ server is stuck processing the requests. Perform a stop action against the Xray server and check if the RabbitMQ is still running. netstat -tulpn would reveal if the RabbitMQ is still listening on port 5672.
If the service is still listening on this port, we need to clear the process and perform a restart of the Xray service. This might help us to clear off the stuck messages.