Hi, I've installed on several customer the AbpBoilerplate versione 1.5 with angular 2. After some time that the site is running, the web site hosted on IIS hangs and is stopped. Also in our stage and production server we have the same error. NetCore version 1.1.2 and DotNetCore.1.0.4_1.1.2-WindowsHosting The event viewer reports the same error:
Application: Uno.Framework.Web.Host.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ObjectDisposedException at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Boolean ByRef) at System.StubHelpers.StubHelpers.SafeHandleAddRef(System.Runtime.InteropServices.SafeHandle, Boolean ByRef) at Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.Libuv+NativeMethods.uv_async_send(Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.UvAsyncHandle) at Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.Libuv.async_send(Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.UvAsyncHandle) at Microsoft.AspNetCore.Server.Kestrel.Internal.KestrelThread.PostCloseHandle(System.Action`1
This is a very big problem because the site after the error is stopped. Can you help us to resolve this issue?
Thank you.
5 Answer(s)
-
0
Hi @ivanosw1,
This might be related to kerstel version. Which version do you use ?
Also, can you check windows event logs ? There might be useful error message which can help us.
Thanks.
-
0
Hi, the Kestrel version is 1.1.1 (file verision 1.1.1.30217). The message I've posted was taken from Event viewer. This morning another customer found the application pool stopped with the same error.
Every time we found Hosting shuthdown the application pool is stopped and in the Event viewer is present the Kestrel error message. Extract from the Abp log trace.
DEBUG 2017-07-16 00:32:35,102 [libuv] Microsoft.AspNetCore.Server.Kestrel - Connection id "0HL6BOPNLHK5E" sending FIN. DEBUG 2017-07-16 00:32:35,102 [libuv] Microsoft.AspNetCore.Server.Kestrel - Connection id "0HL6BOPNLHK5E" sent FIN with status "0". DEBUG 2017-07-16 00:32:35,102 [libuv] Microsoft.AspNetCore.Server.Kestrel - Connection id "0HL6BOPNLHK5E" stopped. DEBUG 2017-07-16 00:51:03,608 [1 ] soft.AspNetCore.Hosting.Internal.WebHost - Hosting shutdown DEBUG 2017-07-17 08:46:02,323 [1 ] Abp.Modules.AbpModuleManager - Loading Abp modules... DEBUG 2017-07-17 08:46:03,048 [1 ] Abp.Modules.AbpModuleManager - Found 25 ABP modules in total. DEBUG 2017-07-17 08:46:03,063 [1 ] Abp.Modules.AbpModuleManager - Loaded module: Uno.Framework.Web.Startup.FrameworkWebHostModule, Uno.Framework.Web.Host, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null DEBUG 2017-07-17 08:46:03,063 [1 ] Abp.Modules.AbpModuleManager - Loaded module: Uno.Framework.Web.FrameworkWebCoreModule, Uno.Framework.Web.Core, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null DEBUG 2017-07-17 08:46:03,063 [1 ] Abp.Modules.AbpModuleManager - Loaded module: Uno.Framework.FrameworkApplicationModule, Uno.Framework.Application, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null DEBUG 2017-07-17 08:46:03,063 [1 ] Abp.Modules.AbpModuleManager - Loaded module: Uno.Framework.FrameworkCoreModule, Uno.Framework.Core, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null DEBUG 2017-07-17 08:46:03,063 [1 ] Abp.Modules.AbpModuleManager - Loaded module: Abp.Zero.AbpZeroCoreModule, Abp.Zero, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null
We are near to panic!!
-
0
Hi,
According to this log message
DEBUG 2017-07-16 00:51:03,608 [1 ] soft.AspNetCore.Hosting.Internal.WebHost - Hosting shutdown
It seems like this is related to ASP.NET Core. Have you searched/reported this in <a class="postlink" href="https://github.com/aspnet/Hosting">https://github.com/aspnet/Hosting</a> ?
Maybe they can help you.
As a temporary workaround, you can try to set IIS apppool to AlwaysOn.
Thanks.
-
0
Thank you. I will try this way.
I wondering if anybody else has the same problems.
-
0
Hi @ivanosw1,
We are hosting angular2 version of AspNet Zero on our servers but didn't have this problem before. Maybe someone else can share their experiences.
Please let us know the result after you try "Always On" setting.
Thanks.
