Registry settings

Few settings can be configured through registry. Settings are stored under:

HKLM\SOFTWARE\Cogin\QueueExplorer

Use roaming profile for settings

UseRoamingProfile DWORD (32-bit), default: 0

If this setting has value larger than zero, QueueExplorer will store settings in roaming folder (C:\Users\<USERNAME>\AppData\Roaming\Cogin\), instead of a local user folder. If settings folder is switched from local to roaming or the other way around, it’s user’s responsibility to copy settings folder to the new location. You can also use “Save project” from the main menu before registry key is changed, and then load saved project after the switch. Note that project file contains only list of connections and doesn’t containt other settings like custom fields, etc.

Pause autorefresh when user is inactive

PauseRefreshAfterIdleMins DWORD (32-bit), default: 0

If this settings has value larger than zero, QueueExplorer will pause all auto refreshes after specified number of minutes of user’s inactivity. When user touches mouse or keyboard we’ll start measuring idle time again. This setting is used to limit server load if QueueExplorer is left turned on for prolonged amount of time without user doing anything on the machine.

RabbitMQ Count Mode

RMQCountMode STRING, values: Auto|Accurate|Fast

Overrides “Message count fetching” setting from RabbitMQ tab in Preferences dialog.

  • Accurate. Unfortunately, this can be slow in certain circumstances but gives us count at that precise moment.

  • Fast. This one is taken from server’s stats, which are generated every 5 seconds by default. So “fast” count can be inaccurate.

  • “Auto” - We fetch count using Fast mode first, and use Accurate only if count is below 100 messages, since it doesn’t seem to affect performance much for these queues.

RabbitMQ reuse connections

RMQReuseConnections DWORD (32-bit), values: 0|1

Overrides “Keep connections open” setting from RabbitMQ tab in Preferences dialog. If set to 1, QueueExplorer will keep connections open and reuse them for all operations. If set to 0, QueueExplorer will open new connection for each operation.

RabbitMQ exclusive mode

RMQExclusiveConsumers DWORD (32-bit), values: 0|1

Overrides “Exclusive consumer” setting from RabbitMQ tab in Preferences dialog. If set to 1, QueueExplorer will use exclusive consumers for all operations. If set to 0, QueueExplorer will use non-exclusive consumers. User can still override it for current message list by using checkbox in toolbar.

See more about RabbitMQ settings in preferences:

Preferences