09-21-2012
acknowledgement in client side with JMS and AMQP
Hi guys,
I have two questions about acknowledgement in client side with JMS and AMQP:
1. what happens if we set CLIENT_ACKNOWLEDGE in producer side in JMS?
2. if basic.publish finishes executing and there is no exception thrown, this means message has been received in message server? or we need to enable transactions or use confirmSelect() to be sure?(I'm using rabbitmq)
3. Is it possible to use txSelect() in consumer side?
Last edited by majid.merkava; 09-21-2012 at 06:32 AM..
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Ive written a java based "webscraper to rss feed" which resides on my college web space when I execute the app from putty it creates the feed and sets the permissions perfectly.I then wrote a php script to execute the app on demand from the browser using
...
system("java -cp... (1 Reply)
Discussion started by: gleesonger
1 Replies
2. Shell Programming and Scripting
Input file_1:
P78811
P40108
O17861
Q6NTW1
P40986
Q6PBK1
P38264
Q6PBK1
Q9CZ49
Q1GZI0
Input file_2: (6 Replies)
Discussion started by: patrick87
6 Replies
3. UNIX for Dummies Questions & Answers
I have identical scripts on two machines: one a laptop running Ubuntu 9.04, and the other a Windows XP desktop running Cygwin. The files I'd like to process are on the Windows machine. Running the script in Cygwin engages eight calls to an external executable and spins off who knows how many forks... (1 Reply)
Discussion started by: SilversleevesX
1 Replies
4. UNIX for Advanced & Expert Users
Folks,
I am trying to solve the following problem. I have a process on machine A running as root that needs to mount and access an NFS partition being exported from machine B.
However, I cannot have 'no_root_squash' option given on B, hence I see NFS requests from machine A end up as 'nobody'... (1 Reply)
Discussion started by: helpmelearn
1 Replies
5. AIX
I have several ssh servers *running aix 5.3 and they respond to sftp requests just fine, but I have one that requires clients to specify the path to the sftp server using the -s flag which is*/usr/sbin/sftp-server
I check the sshd_config across all servers and they are the same. *The other... (1 Reply)
Discussion started by: massdesign
1 Replies
6. Red Hat
When i tried to mount the nfs i see this error message
mount -t nfs 192.168.20.194:/remote/proj1 /nfsmount
mount: 192.168.20.194:/remote/proj1 failed, reason given by server: Permission denied
and the /etc/exports file in the host side looks like this
/remote/proj1 ... (12 Replies)
Discussion started by: srinathk
12 Replies
7. AIX
If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that:
print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3.
My question is... (3 Replies)
Discussion started by: The Doctor
3 Replies
LEARN ABOUT DEBIAN
amqp-consume
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)