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 <[EMAIL PROTECTED]> 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
