Connects to AMQP brokers
AMQP
AMQP Transport
Connects to AMQP brokers
The main AMQP broker host to connect to.
The port to use to connect to the main
AMQP broker.
A comma-separated list of "host:port" or
"host", defining fallback brokers to attempt connection
to, should the connection to main broker fail.
The virtual host to connect to on the
AMQP broker.
The user name to use to connect to the
AMQP broker.
The password to use to connect to the
AMQP broker.
The delivery mode to use when publishing
to the AMQP broker.
The priority to use when publishing to
the AMQP broker.
This flag tells the server how to react
if the message cannot be
routed to a queue. If this flag is
set to true, the server will throw an exception for any
unroutable message. If this flag is false, the server
silently drops the message.
This flag tells the server how to react
if the message cannot be
routed to a queue consumer
immediately. If this flag is set to true, the server
will
throw an exception for any undeliverable message. If
this
flag is false, the server will queue the message, but
with
no guarantee that it will ever be consumed.
Reference to an endpoint to which AMQP
returned message should be
dispatched to.
The acknowledgment mode to use when
consuming from the AMQP broker.
The AMQP broker will consider
messages acknowledged once delivered.
Mule will automatically acknowledge
messages when the flow will have been processed, if
no exception has been encountered.
Using asynchronous
sub-flows or dispatch may lead to early
acknowledgment.
The AMQP broker will expect
explicit message acknowledgments.
The maximum amount of content (measured
in octets) that the server will deliver, 0 if unlimited.
The maximum number of messages that the
server will deliver, 0 if unlimited.
If the no-local field is set the server
will not send messages to the connection that published
them.
Set to true if the connector should only
create exclusive consumers.
Defines if the connector should only do
active exchange and queue declarations or can also perform
passive declarations to enforce their existence.
The exchange to publish to or bind queues to.
Leave blank or omit for the default exchange.
The queue name to consume from. Leave blank
or omit for using a new private exclusive server-named queue.
The routing key to use when binding a queue or publishing a message.
A client-generated consumer tag to establish context.
The type of exchange to be declared.
The durability of the declared exchange.
Specifies if the declared exchange should be
autodeleted.
Specifies if the declared queue is durable.
Specifies if the declared queue should be
autodeleted.
Specifies if the declared queue is exclusive.
Acknowledges the AMQP message that is currently
processed by Mule.
Set to true to acknowledge all messages up to and including the
delivery tag of the AMQP message that is currently
processed by Mule; false to acknowledge just the current
message.
Rejects the AMQP message that is currently
processed by Mule.
Set to true if the rejected message should be requeued rather than discarded/dead-lettered.
Defines the strategy to use to handle messages returned by the AMQP broker.
Destination to which returned messages
will be sent.
The amqpmessage-to-object-transformer element
configures a transformer
that converts an AMQP message into an
object by extracting the
message payload.
The object-to-amqpmessage-transformer element
configures a transformer
that accepts byte[] payloads and copies
outbound message properties to either standard AMQP headers or
custom ones (based on their names).