Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 67372 invoked from network); 22 Mar 2006 14:30:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Mar 2006 14:30:39 -0000 Received: (qmail 74172 invoked by uid 500); 22 Mar 2006 14:30:33 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 74152 invoked by uid 500); 22 Mar 2006 14:30:33 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 74142 invoked by uid 99); 22 Mar 2006 14:30:33 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Mar 2006 06:30:33 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [212.239.14.190] (HELO palantir.servizi.link.it) (212.239.14.190) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Mar 2006 06:30:32 -0800 Received: from gondor.sede-pisa.link.it (pi.link.it. [81.174.15.134]) by palantir.servizi.link.it (8.11.6/8.11.6) with ESMTP id k2MEU6a12225 for ; Wed, 22 Mar 2006 15:30:06 +0100 Received: from wall (wall [131.114.87.14]) by gondor.sede-pisa.link.it (8.11.6/8.11.6) with ESMTP id k2MEU5i20721 for ; Wed, 22 Mar 2006 15:30:05 +0100 Subject: Re: porting from JbossMQ From: Andrea Manca To: activemq-users@geronimo.apache.org In-Reply-To: References: <1142441821.3732.41.camel@wall.sede-pisa.link.it> <1142598475.3725.10.camel@wall.sede-pisa.link.it> <1142605384.3725.21.camel@wall.sede-pisa.link.it> Content-Type: text/plain Date: Wed, 22 Mar 2006 15:28:03 +0100 Message-Id: <1143037683.3725.103.camel@wall.sede-pisa.link.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit X-MailScanner: Found to be clean, Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44), non spam, SpamAssassin (punteggio=0, necessario 5, autolearn=disabled) X-MailScanner-Information: Please contact the ISP for more information X-MailScanner-From: manca@link.it X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I've tried and it's work well. There'is only a problem (i think it could be a bug): if specify -1 as MaximumRedeliveries i expect the broker try to redeliver a message till the end of times ;-). In fact the broker doesn't redeliver anything. Il giorno ven, 17-03-2006 alle 15:20 +0000, James Strachan ha scritto: > Good idea; as an experiment I've tried adding the various redelivery > options to the ActivationSpec. I wonder could you try it out and see > if it works for you? (If you don't want to build from the source you > could wait for tomorrows SNAPSHOT build) > > James > > On 3/17/06, Andrea Manca wrote: > > Il giorno ven, 17-03-2006 alle 12:43 +0000, James Strachan ha scritto: > > > Using Java code you can set the redelivery policy on an ActiveMQConnection > > > or ActiveMQMessageConsumer using the setRedeliveryPolicy() method. Also you > > > can configure it on the ActiveMQResourceAdapter using properties too. > > > > > > We do have some destination specific configuration options that can be used > > > using a handy URI syntax > > > http://activemq.org/Destination+Options > > > > > > Though those currently don't include being able to change the redelivery > > > policy I'm afraid. So to change the redelivery policy on different > > > destinations, I think right now you'll need to use different resource > > > adapters. > > > > > > I don't quite grok how the destination options work yet so am not sure if we > > > can add redelivery policy to them; could you raise a JIRA for this as I > > > think it'd be a handy feature if its not too hard to do. > > > > > > I think could be interesting adding this properties in the activation > > spec of the resource adapter too. In this way the MDB should be able to > > specify the redelivery policy on destination basis without deploy many > > resource adapter. > > I've not many confidence with the AMQ source code, so i don't know if > > this could be a difficult task. -- AM