ConnectionStatusChanged is not fired after server restart

12 views
Skip to first unread message

Wallace Turner

unread,
Oct 5, 2023, 12:00:17 AM10/5/23
to RavenDB - an awesome database
Hi Support we are observing some intermittent behavior in the changes API using 5.4.105 (client & server)

We have a windows process that has wired up `ConnectionStatusChanged`

```
store.Changes().ConnectionStatusChanged += (object sender, EventArgs e) => Log.Info($"ConnectionStatusChanged Connected:{((IDatabaseChanges)sender).Connected}");
```

If we start out process then restart ravendb we consistently see the expected 2 logs statements
```
ConnectionStatusChanged Connected:False
...
ConnectionStatusChanged Connected:True
```
All good so far however we have run into an intermittent issue where the reconnect event is seemingly not fired if ravendb has been running for some time and we restart it - the `Connected:False `is logged but not the subsequent `Connected:True`

Has their been any changes/fixes in this component since 105? We reviewed your change log it doesnt appear so

We don't have a stable recreate as its intermittent but can also report that multiple subsequent restarts of ravendb do not then trigger *any logging* - its as if the event was never wired

Wallace Turner

unread,
Oct 5, 2023, 12:02:28 AM10/5/23
to RavenDB - an awesome database
reposting to github discussions
Reply all
Reply to author
Forward
0 new messages