You can set various headers on the message like 'expire'
http://activemq.apache.org/stomp.html --- R.I.Pienaar > On 15 Jun 2017, at 04:43, Karthi Sweet <kkarthick....@gmail.com> wrote: > > Sorry to bother you again. Looks like the message on queue whatever sent its > simply lying on queue forever when its not getting acked. Is there anyway to > tune activemq/stomp/mcollective properties to delete the messages on queue if > its not consumed by consumer in 5mins of time? > > I saw there is an option on activemq queue properties called > 'expireMessagesPeriod', but I read on some forum as it works based on the ttl > which set during the publish message. > > > >> On Fri, Jun 2, 2017 at 6:32 PM, Karthi Sweet <kkarthick....@gmail.com> wrote: >> It worked! Thank you so much for your time. >> >>> On Fri, Jun 2, 2017 at 1:38 PM, R.I.Pienaar <r...@devco.net> wrote: >>> yes, with normal stomp gem (same as mcollective use) you can do this. >>> >>> >>> client.subscribe("/queue/foo", :ack => "client") >>> >>> msg = client.receive >>> >>> # do stuff with msg >>> >>> # pick whichever version stomp protocol you're using >>> client.ack(msg.headers["ack"]) # stomp 1.2 >>> client.ack(msg.headers["message-id"] # earlier stomp >>> >>> unacked messages goes back to the queue and there are retry counts >>> before they get put into the DLQ >>> >>> >>> On Fri, Jun 2, 2017, at 09:47, Karthi Sweet wrote: >>> > Ok, so you meant to say if I use different client that connects with >>> > stomp >>> > to get messages which will not ack message but still mcollective does the >>> > acking automatically right? please correct me if am wrong >>> > >>> > On Fri, Jun 2, 2017 at 12:56 PM, R.I. Pienaar <r...@devco.net> wrote: >>> > >>> > > If you are doing this with the mco connector libraries then yes it >>> > > effectively auto acks >>> > > >>> > > I have never done anything in mco that would leave messages unacked- >>> > > that >>> > > pattern isn't universal so not something I relied on ever in mco and so >>> > > not >>> > > something the mco connectors can do generally. >>> > > >>> > > --- >>> > > R.I.Pienaar >>> > > >>> > > On 2 Jun 2017, at 04:55, kk21987 <kkarthick....@gmail.com> wrote: >>> > > >>> > > Hi Folks, >>> > > >>> > > Am not sure if this is the right forum to ask this query but still >>> > > mcollective comes into the picture, so believe that asking in right >>> > > place. >>> > > >>> > > Here is scenario am trying, >>> > > >>> > > I have created some automation which will use MCollective module's >>> > > Plugin >>> > > Manager to connect stomp queue and publish the messages like how >>> > > MCollective publishing messages but in different queue name. And I have >>> > > created stomp client which receive messages from the specified queue >>> > > and it >>> > > works perfectly. But the thing is, some cases I don't want to process >>> > > the >>> > > message when it receives and instead I want to process that message >>> > > after >>> > > few mins and till that time it has to be on queue (hardly it has to >>> > > stay in >>> > > queue for 2mins and before I will process it). For this am not >>> > > acknowledging the message when I get from the queue, so theoretically >>> > > when >>> > > I am not ack the message in queue it has to be stay in queue itself, but >>> > > here as soon as the subscriber got the message its getting deleted from >>> > > queue even when am not ack'ing it and its not attempting to redeliver >>> > > it. >>> > > >>> > > So what to understand whether MCollective is ack'ing the message by >>> > > default whether the message is ack'ed or not ack'ed? Is there any way to >>> > > publish the message using MCollective plugin manager with redeliver >>> > > option? >>> > > >>> > > >>> > > Thanks in advance! >>> > > >>> > > -- >>> > > >>> > > --- >>> > > You received this message because you are subscribed to the Google >>> > > Groups >>> > > "mcollective-users" group. >>> > > To unsubscribe from this group and stop receiving emails from it, send >>> > > an >>> > > email to mcollective-users+unsubscr...@googlegroups.com. >>> > > For more options, visit https://groups.google.com/d/optout. >>> > > >>> > > -- >>> > > >>> > > --- >>> > > You received this message because you are subscribed to a topic in the >>> > > Google Groups "mcollective-users" group. >>> > > To unsubscribe from this topic, visit https://groups.google.com/d/ >>> > > topic/mcollective-users/Snqz-6l_fcY/unsubscribe. >>> > > To unsubscribe from this group and all its topics, send an email to >>> > > mcollective-users+unsubscr...@googlegroups.com. >>> > > For more options, visit https://groups.google.com/d/optout. >>> > > >>> > >>> > -- >>> > >>> > --- >>> > You received this message because you are subscribed to the Google Groups >>> > "mcollective-users" group. >>> > To unsubscribe from this group and stop receiving emails from it, send an >>> > email to mcollective-users+unsubscr...@googlegroups.com. >>> > For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> R.I.Pienaar / www.devco.net / @ripienaar >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "mcollective-users" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/mcollective-users/Snqz-6l_fcY/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> mcollective-users+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> > > -- > > --- > You received this message because you are subscribed to the Google Groups > "mcollective-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mcollective-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mcollective-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
