Skip to end of metadata
Go to start of metadata

This page describes RabbitMQ, an implementation of an AMQP broker.

Use in Release 2

For Release 2, ION is using AMQP 0.9.1 and RabbitMQ-Server v. 2.8.x on CentOS 6.x

Use of VHOST:

The system uses the default VHOST '/'

Use of Exchanges:

Exchange
Type
Description

TBD

Authentication:

TBD

Use in Release 1

For Release 1, ION is using AMQP 0.9.1 and RabbitMQ-Server v. 2.3.1 on CentOS 5.5

Use of VHOST:

The system uses the default VHOST '/'

Use of Exchanges:

Exchange
Type
Description
magnet.topic
topic
ION service traffic. Routing keys are equivalent to the global sysname qualified identifiers for service and process names.
events.topic
topic
ION Exchange Point for events
science_data.topic
topic
ION Exchange Point for science data (managed by the PubsubControllerService)

Authentication:

TBD

Description

RabbitMQ is an Open Source implementation of an AMQP broker (currently supports AMQP 0.8, 0.9, 0.9.1).

AMQP is implemented in Erlang/OTP and requires an Erlang VM installation.

RabbitMQ Details

Queue Browsing (Introspection):

In general, AMQP 0.9.1 does not support queue browsing.

See:

There are 2 "hack" work arounds:

  • Consume messages and reject afterwards (with requeue=True). Potentially loses message FIFO order. Will not redeliver to the same consumer
    • Quirk (observed in Rabbit 2.7.1): the broker is not supposed to redeliver that message, but it appears that it waits until you get another message in the queue, then it will redeliver to the same consumer.
  • Consume messages (with auto-ack=False) and not ACK and cancel the channel. The next consumer will get the messages again
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.