Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 70458 invoked from network); 14 Dec 2010 17:07:44 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 Dec 2010 17:07:44 -0000 Received: (qmail 7636 invoked by uid 500); 14 Dec 2010 17:07:44 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 7582 invoked by uid 500); 14 Dec 2010 17:07:43 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 7574 invoked by uid 99); 14 Dec 2010 17:07:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Dec 2010 17:07:43 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of marnie.mccormack@googlemail.com designates 209.85.212.177 as permitted sender) Received: from [209.85.212.177] (HELO mail-px0-f177.google.com) (209.85.212.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Dec 2010 17:07:38 +0000 Received: by pxi7 with SMTP id 7so195255pxi.22 for ; Tue, 14 Dec 2010 09:07:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=k/tAFvk4eAH3vsJUXPvEBCKhM3DRUTSSQ6Sze1uqibE=; b=HN26t+tPJGV9SxpVvuRjpnEmMak6byatCG5A7/BGE9sSQpvCfILH5yMmkv15UKkC6l 9B8u7qZEjtklqPG5oVR1GyD75rSWyiRzPRJhXFbp0NkgWSpyVquNkOjJPz3nC9ZLGzNd yNWQpxY/74gJXEi0y9jc1gSJ0Qh9SUomaDRLg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=x9CqEn8uSelU38T/Czu5VWzss8LyO2KXBbcRcWHRUbMJUk7OEOcpez2NzqOo/M4qvl hlOndf+ZvkRvwr/426IIdBo7CCT9il87xRSoBG7T01jHjIaxJjgs76ZR4VTiedpGmLbH +gszCnqGX2tEDnvZGvdu89Y0vXsL5UKTjP0sw= MIME-Version: 1.0 Received: by 10.143.167.11 with SMTP id u11mr4654108wfo.193.1292346437901; Tue, 14 Dec 2010 09:07:17 -0800 (PST) Received: by 10.142.70.16 with HTTP; Tue, 14 Dec 2010 09:07:17 -0800 (PST) In-Reply-To: <0cd8a675914eb491bd87d267f4e09378@i-a-i.com> References: <0cd8a675914eb491bd87d267f4e09378@i-a-i.com> Date: Tue, 14 Dec 2010 17:07:17 +0000 Message-ID: Subject: Re: Confirm Broker received message from Producer? (Java client and broker) From: Marnie McCormack To: users@qpid.apache.org Content-Type: multipart/alternative; boundary=001636e910675b9f34049761da1b --001636e910675b9f34049761da1b Content-Type: text/plain; charset=ISO-8859-1 So if the transaction commit fails you'll get a JMSException thrown back to the client. The producing application can then choose to attempt rollback and/or retry the send. (Obviously, limited retry is a good idea to avoid thrashing). More likely htough is that the failure will cause the Producer's connection to be dropped - since any condition causing transactions to fail most likely to be considered fatal. Timeout is the most common cause of a commit failure, and would usually reflect system load or network issues. In the Qpid client example packages, there are various publisher classes in the publisher package with examples of handling exceptions on commit for a transacted send. hth, Marnie On Tue, Dec 14, 2010 at 3:44 PM, William Drozd wrote: > > Thanks Marnie!, > > > I appreciate the help. I have a follow-up question though, if the > Transaction fails what happens from the Publisher's perspective? > > > > Thanks again, > Bill > > > -----Original Message----- > From: Marnie McCormack [mailto:marnie.mccormack@googlemail.com] > Sent: Tuesday, December 14, 2010 10:26 AM > To: users@qpid.apache.org > Subject: Re: Confirm Broker received message from Producer? (Java client > and broker) > > Hi Bill, > > Transactions are the way to go here, for the simplest solution. > > The transaction will return on the send() once the message has been > received > and processed (i.e. persisted etc ) on the broker. > > The JMS API exposes the Connection.createSession (transacted, > acknowledeMode) method - set transacted to true on the MessageProducer's > session. > > Regards, > Marnie > > On Tue, Dec 14, 2010 at 2:38 PM, William Drozd wrote: > > > Hello, > > > > For the Java client and Java Broker: > > > > When a producer sends a message to a Broker, is there any way to confirm > > that the Broker received the message in the Producer? Ideally, I am > looking > > for some type of ACK call-back after the Broker receives the Producer's > > message. > > > > Thanks, > > Bill > > > > > > > > > > > > > > > __________________________________________________________________________ > > This message and all attachments are PRIVATE, and contain information > that > > is PROPRIETARY to Intelligent Automation, Inc. You are not authorized to > > transmit or otherwise disclose this message or any attachments to any > > third party whatsoever without the express written consent of Intelligent > > Automation, Inc. If you received this message in error or you are not > > willing to view this message or any attachments on a confidential basis, > > please immediately delete this email and any attachments and notify > > Intelligent Automation, Inc. > > > > > > --------------------------------------------------------------------- > > Apache Qpid - AMQP Messaging Implementation > > Project: http://qpid.apache.org > > Use/Interact: mailto:users-subscribe@qpid.apache.org > > > > > > > __________________________________________________________________________ > This message and all attachments are PRIVATE, and contain information that > is PROPRIETARY to Intelligent Automation, Inc. You are not authorized to > transmit or otherwise disclose this message or any attachments to any > third party whatsoever without the express written consent of Intelligent > Automation, Inc. If you received this message in error or you are not > willing to view this message or any attachments on a confidential basis, > please immediately delete this email and any attachments and notify > Intelligent Automation, Inc. > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:users-subscribe@qpid.apache.org > > --001636e910675b9f34049761da1b--