-
-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service Error #187
Comments
Hi, thanks for the report. I modified in 2.7.0 the way to notify a session disconnect (https://github.com/cedrozor/myrtille/blob/master/Myrtille.Services/RemoteSessionProcess.cs#L455). It was to avoid deadlocks occuring in some rare cases when invoking the callback of a WCF duplex channel; but that's not good if it brings new issues :/ I will investigate and, at least, have the async task instanciation into a try/catch block so that it doesn't crash Myrtille.Services.exe. |
…a disconnect notification (#187, thanks gtmsew) the automatic application pool recycling is now disabled by default, and is not applicable if using the enterprise mode (this prevents enterprise sessions to be dropped unexpectedly!) if recycling is enabled, a new http session is now acquired on disconnect; this prevents a subsequent login failure (due to the old http session being invalid) without any error message
Did you had the issue happening again? |
It was one-time error for me. |
Well... anyway, I improved the exception handling around that call, so it shouldn't happen again |
Hi, on the 2.7.0 today morning service on one of the server hang with below error details in Even Log:
Setup info:
OS: Windows Server 2016
Type: VM on GCP
Hardware info: 6*CPU + 14GB RAM + 250GB SSD
Roles Installed: IIS, AD
This server works as a gateway to the RDS server
At that time there were around 10 users connected.
I did not find anything in the Myrtille Service Log, and when I started the service everything started to work normally. Currently I set up the service to try to recovery after fail, however it would be great to prevent this to happend in the future ;)
The text was updated successfully, but these errors were encountered: