Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 24442 invoked from network); 20 Apr 2010 08:47:28 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Apr 2010 08:47:28 -0000 Received: (qmail 92220 invoked by uid 500); 20 Apr 2010 08:47:28 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 92084 invoked by uid 500); 20 Apr 2010 08:47:26 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 92068 invoked by uid 99); 20 Apr 2010 08:47:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Apr 2010 08:47:25 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Sachindra.Nath@efi.com designates 192.68.228.96 as permitted sender) Received: from [192.68.228.96] (HELO mail5.efi.com) (192.68.228.96) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Apr 2010 08:47:19 +0000 Received: from fcexhub01.efi.internal (10.3.12.16) by mail5.efi.com (192.68.228.96) with Microsoft SMTP Server (TLS) id 8.2.234.1; Tue, 20 Apr 2010 01:46:59 -0700 Received: from FCEXMB02CCR.efi.internal ([10.3.12.105]) by fcexhub01.efi.internal ([10.3.12.16]) with mapi; Tue, 20 Apr 2010 01:46:58 -0700 From: Sachindra Nath To: "users@activemq.apache.org" Date: Tue, 20 Apr 2010 01:46:51 -0700 Subject: RE: ActiveMQ RA: how to make MDB with CLIENT_ACKNOWLEDGE? Thread-Topic: ActiveMQ RA: how to make MDB with CLIENT_ACKNOWLEDGE? Thread-Index: Acrfu3mM2b3lMKxwTPyqy1xNfpu4ZAAqle+A Message-ID: References: <28287660.post@talk.nabble.com> In-Reply-To: <28287660.post@talk.nabble.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-cr-hashedpuzzle: AOMN BUSC BndQ BuB5 B3Am CFOw CkZv Dk/1 D4Go Exn5 GYgD HoYb IT/B JAGK JohC JpGc;1;dQBzAGUAcgBzAEAAYQBjAHQAaQB2AGUAbQBxAC4AYQBwAGEAYwBoAGUALgBvAHIAZwA=;Sosha1_v1;7;{48E600D9-2919-4DF7-AD5A-DAED9B6C7F7B};cwBhAGMAaABpAG4AZAByAGEALgBuAGEAdABoAEAAZQBmAGkALgBjAG8AbQA=;Tue, 20 Apr 2010 08:46:51 GMT;UgBFADoAIABBAGMAdABpAHYAZQBNAFEAIABSAEEAOgAgAGgAbwB3ACAAdABvACAAbQBhAGsAZQAgAE0ARABCACAAdwBpAHQAaAAgAEMATABJAEUATgBUAF8AQQBDAEsATgBPAFcATABFAEQARwBFAD8A x-cr-puzzleid: {48E600D9-2919-4DF7-AD5A-DAED9B6C7F7B} acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi Ivan, You can't do that. It'd be against the EJB specifications. See below: 5.4.14 Message Acknowledgment for JMS Message-Driven Beans JMS message-driven beans should not attempt to use the JMS API for message = acknowledgment. Message acknowledgment is automatically handled by the container. If the message-dr= iven bean uses container- managed transaction demarcation, message acknowledgment is handled automati= cally as a part of the transaction commit. If bean-managed transaction demarcation is used, th= e message receipt cannot be part of the bean-managed transaction, and, in this case, the receipt is ack= nowledged by the container. If bean-managed transaction demarcation is used, the Bean Provider can indicat= e whether JMS AUTO_ACKNOWLEDGE semantics or DUPS_OK_ACKNOWLEDGE semantics should apply by= using the activationConfig element of the MessageDriven annotation or by using the ac= tivation- config-property deployment descriptor element. The property name used to sp= ecify the acknowledgment mode is acknowledgeMode. If the acknowledgeMode property is = not specified, JMS AUTO_ACKNOWLEDGE semantics are assumed. The value of the acknowledgeMod= e property must be either Auto-acknowledge or Dups-ok-acknowledge for a JMS message-dr= iven bean. Regards Sachindra -----Original Message----- From: Ivan Pechorin [mailto:ivan.pechorin@gmail.com] Sent: Monday, April 19, 2010 5:56 PM To: users@activemq.apache.org Subject: ActiveMQ RA: how to make MDB with CLIENT_ACKNOWLEDGE? Hello We have a message-driven bean in JBoss with ActiveMQ resource adapter (RA). It seems like ActiveMQ RA doesn't support CLIENT_ACKNOWLEDGE mode. It supports only DUPS_OK_ACKNOWLEDGE and AUTO_ACKNOWLEDGE modes. Basically, I need to be able to leave a message in queue if something bad happened inside method onMessage() of my MDB. How can I achieve this? P.S. Any help of link to proper piece of documentation is highly appreciate= d (I failed to find it). Best regards, Ivan -- View this message in context: http://old.nabble.com/ActiveMQ-RA%3A-how-to-m= ake-MDB-with-CLIENT_ACKNOWLEDGE--tp28287660p28287660.html Sent from the ActiveMQ - User mailing list archive at Nabble.com. Confidentiality notice: This message may contain confidential information.= It is intended only for the person to whom it is addressed. If you are no= t that person, you should not use this message. We request that you notify= us by replying to this message, and then delete all copies including any c= ontained in your reply. Thank you.