well, I am capturing the exception and if there is any, I re-enqueue it :-)
not elegant, again :-) but seems to work I wish I could have it automatically. It´s not how it´s supposed to be TIA Leo On Tue, Jul 9, 2013 at 10:06 PM, Howard W. Smith, Jr. <[email protected]> wrote: > Leo, > > is this still an issue for you? in the other thread, i think you said > everything is working well now. right? > > Howard > > > > On Tue, Jul 9, 2013 at 8:46 AM, Leonardo K. Shikida <[email protected]>wrote: > >> Hi >> >> I don't want that dead messages go to the queue://ActiveMQ.DLQ. >> Instead, I'd like to re-enqueue these messages indefinitely. Here's >> how it looks like >> >> <Resource id="MyJmsResourceAdapter" type="ActiveMQResourceAdapter"> >> BrokerXmlConfig = >> broker:(tcp://localhost:61616)?persistent=true >> ServerUrl = tcp://localhost:61616 >> DataSource = MyJmsDataSource >> maximumRedeliveries -1 >> </Resource> >> >> also tried >> >> <Resource id="MyJmsResourceAdapter" type="ActiveMQResourceAdapter"> >> BrokerXmlConfig = >> broker:(tcp://localhost:61616)?persistent=true >> ServerUrl = tcp://localhost:61616 >> DataSource = MyJmsDataSource >> maximumRedeliveries = -1 >> </Resource> >> >> acknowledge is auto >> >> session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); >> >> although it's not re-enqueueing. How do I configure tomee.xml properly >> to do that? >> >> TIA >> >> Leo >>
