Hello, we have a .net core app which we recently migragated to 2.1 from 1.x. Post migration we have seen that the app hangs everytime we recycle the application pool, the app can’t be reached and only resolution to this is to stop the app pool, kill dotnet.exe,
and the start the pool. After few hours of investigation we found out some exceptions which says the app was unable to write to loggers - because of an Ssl connection issue. We use Microsoft.Logging.Extensions and send these to Splunk over https using the
configuration from appsettings json file. This is intermittent, as after few restarts of the app pool it behaves fine. Even it remains stable for few hours or even days before it goes down again.
After we commented out the code to add this Splunk logging at the startup the app runs just fine and shows no issues on app pool recycling, behaves exactly how it should. We derived from this behaviour that the Splunk connection issue might be causing the app to hang? We also found out a post which says that there might be a issue with asp.net core 2.1 regarding the ssl issue I mentioned?
I would really appreciate if someone can throw some light and help us find the correct solution.
After we commented out the code to add this Splunk logging at the startup the app runs just fine and shows no issues on app pool recycling, behaves exactly how it should. We derived from this behaviour that the Splunk connection issue might be causing the app to hang? We also found out a post which says that there might be a issue with asp.net core 2.1 regarding the ssl issue I mentioned?
I would really appreciate if someone can throw some light and help us find the correct solution.