acknowledgement in client side with JMS and AMQP


 
Thread Tools Search this Thread
Top Forums Programming acknowledgement in client side with JMS and AMQP
# 1  
Old 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..
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. AIX

Kdb - vscsi disk mapping from AIX 5.3 CLIENT side

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

2. Red Hat

Not able to mount NFS share on client side

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

3. AIX

sftp : have to specify subsystem from client side

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

4. UNIX for Advanced & Expert Users

NFS client-side userid mapping

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. UNIX for Dummies Questions & Answers

SSH using the shell on the client side -- possible?

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

6. Shell Programming and Scripting

Paste two file side by side together based on specific pattern match problem

Input file_1: P78811 P40108 O17861 Q6NTW1 P40986 Q6PBK1 P38264 Q6PBK1 Q9CZ49 Q1GZI0 Input file_2: (6 Replies)
Discussion started by: patrick87
6 Replies

7. UNIX for Dummies Questions & Answers

Running server side application on client demand

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
Login or Register to Ask a Question
AMQP-PUBLISH(1) 						 RabbitMQ C Client						   AMQP-PUBLISH(1)

NAME
amqp-publish - Publish a message on an AMQP server SYNOPSIS
amqp-publish [OPTION...] DESCRIPTION
Publishes a message to an exchange on an AMQP server. Options allow the various properties of the message and parameters of the AMQP basic.publish method to be specified. By default, the message body is read from standard input. Alternatively, the -b option allows the message body to be provided as part of the command. OPTIONS
-e, --exchange=exchange name The name of the exchange to publish to. If omitted, the default exchange (also known as the nameless exchange) is used. -r, --routing-key=routing key The routing key to publish with. If omitted, an empty routing key is assumed. A routing key must be specified when publishing to the default exchange; in that case, accoding to the AMQP specification, the routing key corresponds to a queue name. -p, --persistent Use the persistent delivery mode. Without this option, non-persistent delivery is used. -C, --content-type=MIME type Specifies the content-type property for the message. If omitted, the content-type property is not set on the message. -E, --content-encoding=content coding Specifies the content-encoding property for the message. If omitted, the content-encoding property is not set on the message. -b, --body=message body Specifies the message body. If omitted, the message body is read from standard input. EXAMPLES
Send a short message, consisting of the word "Hello" to the queue "myqueue" via the default exchange: $ amqp-publish -r myqueue -b Hello Send some XML data from a file to the exchange "events", with persistent delivery mode, setting the content-type property on the message to make the data format explicit: $ amqp-publish -e events -p -C text/xml <event.xml 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-PUBLISH(1)