Jiri Cincura ↹

Let me see whether I'll be able to reproduce it on my side.

@AlexGreenZ I wasn't able to replicate the issue with your setup and code.

@mrjohnr I wasn't able to replicate the issue with your setup and code.

Yes, in both cases I was running instance on a separate machine (even outside local network).

Also new datatypes.

No specific FB4 features are surfaced for EF Core. Other than that, I'm not aware of any blocker regarding EF Core and FB4.

@lweberprb (hope I found the right person) That's interesting scenario. Because when you shutdown the database, the connection (socket) is not closed. But only after next operation the error is...

Yeah, watchdog-like handling is common approach people use when using events. I was playing with similar approach. The idea was to wait for any response from server for limited time...

OK, looks like there's nothing on protocol level that would help this situation. And I'm not sure whether periodically re-asking for events is a good idea. Especially because it relies...

I'm closing it now. Some kind of watchdog/heartbeat/... is required from developer. But I'll reopen if there's some new light shed onto this problem.