You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are running a suite of tests using storyteller and serenity system on a Windows 2012 R2 system. The tests seem to be unable to run and the data I have gathered points to a problem in Fubu Hosting or Serenity. It seems that our site is successfully running, based on logs, but that any attempt to connect results in a
System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
After more digging I was able to turn on Katana's logging and we receive this error consistently
Microsoft.Owin.Host.HttpListener.OwinHttpListener Error: 0 : Accept
System.Net.HttpListenerException (0x80004005): The I/O operation has been aborted because of either a thread exit or an application request
at System.Net.HttpListener.EndGetContext(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Owin.Host.HttpListener.OwinHttpListener.<ProcessRequestsAsync>d__0.MoveNext()
ProcessId=8916
DateTime=2018-06-18T19:27:42.1284755Z
If there is any configuration we can change on our side to help figure out what is wrong, we can do that. Any help is appreciated.
The text was updated successfully, but these errors were encountered:
We are running a suite of tests using storyteller and serenity system on a Windows 2012 R2 system. The tests seem to be unable to run and the data I have gathered points to a problem in Fubu Hosting or Serenity. It seems that our site is successfully running, based on logs, but that any attempt to connect results in a
After more digging I was able to turn on Katana's logging and we receive this error consistently
If there is any configuration we can change on our side to help figure out what is wrong, we can do that. Any help is appreciated.
The text was updated successfully, but these errors were encountered: