Yes. Chris McDermott Remote Business Analytics STaTS/StoreFront Remote HPE Storage Hewlett Packard Enterprise Mobile: +1 978-697-5315
On 9/14/16, 9:54 AM, "Oleg Zhurakousky" <[email protected]> wrote: So you’re asking about ConsumeJMS? > On Sep 14, 2016, at 9:49 AM, McDermott, Chris Kevin (MSDU - STaTS/StorefrontRemote) <[email protected]> wrote: > > Hi Oleg, > > Sorry, I wasn’t more clear. I should have stated that ConsumeJMS does not expose a setting for ACK mode. Screen shot attached. So my question is which ACK mode does it use? > > Thanks, > > Chris McDermott > > Remote Business Analytics > STaTS/StoreFront Remote > HPE Storage > Hewlett Packard Enterprise > Mobile: +1 978-697-5315 > > > > > On 9/14/16, 9:41 AM, "Oleg Zhurakousky" <[email protected]> wrote: > > Chris > > FWIW, the Get/PutJMS* are effectively deprecated processors since they only support one JMS provider (ActiiveMQ) and should not be used. Instead we recommend Publish/ConsumeJMS pair. > > As to your question, which specific ACK mode you are inquiring about? As the doc currently states, the auto-ACK may loose messages. Is that what you are using? > > Cheers > Oleg > > On Sep 14, 2016, at 9:28 AM, McDermott, Chris Kevin (MSDU - STaTS/StorefrontRemote) <[email protected]<mailto:[email protected]>> wrote: > > > Hey folks, > > The GetJMSQueue processor allows configuration of the Acknowledgment Mode. > > Acknowledgement Mode > > Client Acknowledge > > • Client Acknowledge > • Auto Acknowledge > > The JMS Acknowledgement Mode. Using Auto Acknowledge can cause messages to be lost on restart of NiFi but may provide better performance than Client Acknowledge. > > > Can someone speak to how Acknowledgement Mode is handled by the ConsumeJMS processor? > > The reason I ask is that I seem to be losing messages on NiFi restart. > > Thanks, > Chris McDermott > > Remote Business Analytics > STaTS/StoreFront Remote > HPE Storage > Hewlett Packard Enterprise > Mobile: +1 978-697-5315 > > > > >
