Closed mm201 closed 3 years ago
Relevant stackoverflow post: https://stackoverflow.com/questions/1986292/a-timeout-was-reached-while-waiting-for-the-service-to-connect-error-after-reb
It seems lock()s aren't to blame after all. If they were, the server startup message would be logged but it isn't.
Targeting .NET 2.0 has sped up the launch time by a huge amount so I'll mark this resolved and reopen if it crashes again.
I can't replicate locally (of course) but it happens in production every time the server restarts. It hangs when the service is automatically started after a reboot but starting it manually seems to work.
lock()s are probably to blame. e.g. in
GTServerBase.BeginPolling()
.