Messages will go to the DLQ because the redelivery count is > the configured. The message will be redelivered because the client rejected it...
Different than OpenWire messages, messages are redelivered through the server, always.. on OpenWire the client will redeliver the message and the client would be able to set the cause if any... on Artemis.. messages will always go back to the server.. so there is no coupling between the two that would allow you to setup the cause anywhere. Even though in OpenWire you can probably only do that on MDBs as the Resource Adapter would catch the exceptions.. any other mechanism and you won't have a hook to capture anything. On Tue, May 23, 2017 at 8:59 AM, Justin Bertram <jbert...@apache.org> wrote: > There are currently no plans to add that feature. However, feel free to open > a JIRA and (even better) send a PR to implement the functionality. > > > Justin > > ----- Original Message ----- > From: "vishal3007" <vishal3...@gmail.com> > To: users@activemq.apache.org > Sent: Monday, May 22, 2017 11:32:45 PM > Subject: Re: ActiveMQ Artemis: failure cause of DLQ messages > > Thanks for quick response... > Any plan for adding such feature as I can see that similar feature is > available in ActiveMQ? https://issues.apache.org/jira/browse/AMQ-3236 > > Thanks, > Vishal > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Artemis-failure-cause-of-DLQ-messages-tp4726423p4726436.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Clebert Suconic
