RabbitMQ 1.3.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News RabbitMQ 1.3.0 (Default branch)
# 1  
Old 04-02-2008
RabbitMQ 1.3.0 (Default branch)

RabbitMQ is an implementation of AMQP, the emerging standard for high performance enterprise messaging. The RabbitMQ server is based on a proven platform, Erlang/OTP, offering exceptionally high reliability, availability, and scalability. It delivers good throughput and latency performance that is predictable and consistent. The code base is compact and easily maintainable, facilitating rapid customization and hot deployment. The RabbitMQ distribution also includes a Java client that interoperates with any compliant AMQP server. License: Mozilla Public License (MPL) Changes:
This release fixes a number of race conditions and other bugs, improves performance, and has better error reporting.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

OpenMQ, ActiveMQ or RabbitMQ

I am trying to form a proper proposal for my project however I do not know exactly what I can do. I was thinking whether I could work on a client side library which enables that client to connect to a known broker such as OpenMQ or ActiveMQ. Have you got any ideas which may be the best client,... (0 Replies)
Discussion started by: tyron
0 Replies
Login or Register to Ask a Question
AMQP-CONSUME(1) 						 RabbitMQ C Client						   AMQP-CONSUME(1)

NAME
amqp-consume - Consume messages from a queue on an AMQP server SYNOPSIS
amqp-consume [OPTION...] {command} [args...] DESCRIPTION
amqp-consume consumes messages from a queue on an AMQP server. For each message that arrives, a receiving command is run, with the message body supplied to it on standard input. amqp-consume can consume from an existing queue, or it can create a new queue. It can optionally bind the queue to an existing exchange. By default, messages will be consumed with explicit acknowledgements. A message will only be acknowledged if the receiving command exits successfully (i.e. with an exit code of zero). The AMQP "no ack" mode (a.k.a. auto-ack mode) can be enable with the -A option. OPTIONS
-q, --queue=queue name The name of the queue to consume messages from. If the --queue option is omitted, the AMQP server will assign a unique name to the queue, and that server-assigned name will be dixsplayed on stderr; this case implies that an exclusive queue should be declared. -e, --exchange=exchange name Specifies that an exclusive queue should be declared, and bound to the given exchange. The specified exchange should already exist unless the --exchange-type option is used to request the creation of an exchange. -r, --routing-key=routing key The routing key for binding. If omitted, an empty routing key is assumed. -d, --declare Forces an exclusive queue to be declared, even when it otherwise would not be. That is, when a queue name is specified with the --queue option, but no binding to an exchange is requested with the --exchange option. -A, --no-ack=routing key Enable "no ack" mode: The AMQP server will unconditionally acknowledge each message that is delivered, regardless of whether the target command exits successfully or not. EXAMPLES
Consume messages from an existing queue "myqueue", and output the message bodies on standard output via cat: $ amqp-publish -q myqueue cat Bind a new exclusive queue to an exchange "myexch", and send each message body to the script myscript, automatically acknowledging them on the server: $ amqp-consume -A -e myexch ./myscript SEE ALSO
librabbitmq-tools(7) describes connection-related options common to all the RabbitMQ C Client tools. AUTHOR
The RabbitMQ Team <info@rabbitmq.com> RabbitMQ C Client 2011-01-01 AMQP-CONSUME(1)