User Tools

Site Tools


development:applications:ebonding:howto:rabbitmqgui

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
development:applications:ebonding:howto:rabbitmqgui [2017/02/03 13:45] bcoffeydevelopment:applications:ebonding:howto:rabbitmqgui [2021/06/25 10:09] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== RabbitMQ GUI ======
 +Author : Brian Coffey
 +\\ Date : 2017-02-03
 +
 +==== Overview ====
 +The RabbitMQ GUI shown below can be accessed from port 15672 and is currently only active on ExteNet server - it is usually run on the loadbalancer 
 +
 +{{:development:applications:ebonding:howto:rabbit_gui.png|}}
 +
 +==== Queues ====
 +The queues currently present for eBonding are shown below. Currently 4 queues are implemented; eBonding inbound, eBonding outbound, ticketer inbound, soap outbound. These queues are explained in more detail at [[development:applications:ebonding:works|eBonding - How it Works]]. Clicking inside these queues through the GUI gives visual information of messages on the queue. One important parameter for the queue is its consumer. A queue without a consumer means messages will become stuck on that queue and won't traverse the Soap-eBonding-Ticketer trip. This is something to be aware of if the logs show messages getting stuck at one particular point without an explicit exception other than a timeout.
 +
 +{{:development:applications:ebonding:howto:queues.png ?1000}}
 +