You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an application that is connecting to event store and listening on a persistent subscription. I have observed a failure mode where the subscription seems to "hang". When I look at the event store web UI, I can see my application is connected but the status icon is red, and the current event number is less than the known event number.
Trying to get the application to re-connect, I tried updating the persistent subscription in the event store UI without changing any of the values. As expected, this triggered the eventstore to close any open connections, but the client code in your library experiences a panic while trying to call my SubscriptionDroppedHandler. I believe the issue stems from dto.Reason being a nill pointer.
The questions remain, what causes the client to get hung up and stop processing messages? Also, why is the dto.Reason field nil when handling the subscription dropping?
Attached is my stack trace the application throws.
I have an application that is connecting to event store and listening on a persistent subscription. I have observed a failure mode where the subscription seems to "hang". When I look at the event store web UI, I can see my application is connected but the status icon is red, and the
current
event number is less than theknown
event number.Trying to get the application to re-connect, I tried updating the persistent subscription in the event store UI without changing any of the values. As expected, this triggered the eventstore to close any open connections, but the client code in your library experiences a panic while trying to call my SubscriptionDroppedHandler. I believe the issue stems from
dto.Reason
being a nill pointer.The questions remain, what causes the client to get hung up and stop processing messages? Also, why is the
dto.Reason
field nil when handling the subscription dropping?Attached is my stack trace the application throws.
This application is being run in docker on Alpine 3.8 against Event Store 4.1.4, which is also in docker.
The text was updated successfully, but these errors were encountered: