Clarification of PersistentSubscriptionNakEventAction.Stop

[quorak]

Hey there,

I'm having a PersistentSubscription and while catching up, I come into the situation, that I cannot process a certain Event. I would like to stop the persistentSubscription at the event where it is and continue at a later point (order is important).

I though subscription.fail(event,PersistentSubscriptionNakEventAction.Stop,'Error in sub service') would be the right choice. But Events keep on bubbeling in and get acknowledged to the eventstore.

I tried all combinations of the PersistentSubscription Settings, but weven with a 1000 Events to catch up, the subscription iterates throuh all of them, no matter how often I call sub.fail... Did I misunderstood the concept ? Any clarification is appreciated.

[nicdex]

Did you disable autoAck on the persistent subscription?
By default persistent subscription are automatically acknowledge, so that would explain the behavior.
Use false as the last parameters in connectToPersistentSubscription(stream, groupName, eventAppeared, subscriptionDropped, userCredentials, bufferSize, autoAck)

[morrislaptop]

EventStore will essentially just record that an event was not acknowledged. You can then use the Replayed Parked Messages in the admin ui to stream those events back to the subscription?

[quorak]

hey there, thanks for the replay.

Yes i disabled autoAck. I want to have more control over the acknowledgement.

• I would also like to park some of the unprocessable entities at time.
• And in certain situations I want to Stop the incoming messages in a controlled manner (e.g. a subsequent service is unreachable) and continue at a later point

Isn't this what PersistentSubscriptionNakEventAction.Stop was thought for, or am i mistaken.

thanks a lot.

[tombako]

Hello, we also struggling to understand concept behind PersistentSubscriptionNakEventAction.Stop. We also as this original problem describes, would like to stop subscription if certain events cannot be processed. Any suggestions here?