Diagnostic utility for checking the status of the RabbitMQ platform service

Discussion created by rsunderman-esristaff Employee on May 22, 2015
Latest reply on Dec 19, 2017 by Will_Hughes-esristaff
Branched from an earlier discussion
Branched to a new discussion

There is a very basic utility bundled with the Clustering tutorial which will request a status from the RabbitMQ platform service, attempt to connect, and send a message to see if the specified host is able to receive messages.


Please download and unzip the attached to a local folder on the server on which you have installed ArcGIS Server and the GeoEvent Extension. Open a Windows command shell and change directory to the folder containing the files you extracted from the ZIP archive.


In your Windows command shell, execute the commands illustrated below:



You should see the following usage instructions:


  • Enter the Machine name, Port, Admin user and admin password, separated by a space.
  • (For example: “machine 6080 admin admin_pass):


I tend to specify a fully qualified server name and domain (e.g. - and because my ArcGIS Server is configured to allow HTTPS connections - I specify port 6443. You could also specify localhost and port 6080 if your ArcGIS Server is only configured for HTTP connections.


If the utility is able to retrieve a status from the RabbitMQ platform service, connect, and receive a test message, you should see messages like the ones illustrated below:




Update March 2017:

The diagnostic utility rabbitmqdiag-1.0.jar is throwing a com.esri.arcgis.discovery exception when run against the 10.5 release of ArcGIS Server. Users have reported the same exception being thrown when the utility is run against the 10.4.1 release. The GeoEvent product team does not have the source code for this utility. It was provided as an elementary diagnostic to the GeoEvent team when RabbitMQ was first being integrated. It is not actually part of either the ArcGIS Server product or the GeoEvent Server product and is not being supported. If a new utility can be developed for the 10.5 product release comments will be added to this thread; otherwise please assume that the utility will only work for a 10.3.x product deployment.