2017-11-16 00-34-54
Prakash Behera
711Views
4Comments
There is no longer an HttpContext available.
Question



we are getting these errors. Could someone please help me to know what is this error about and how can we resolve this.


The client is disconnected because the underlying request has been completed.  There is no longer an HttpContext available.


   at System.Web.HttpBufferlessInputStream.Read(Byte[] buffer, Int32 offset, Int32 count)
   at System.Web.Http.WebHost.SeekableBufferedRequestStream.Read(Byte[] buffer, Int32 offset, Int32 count)
   at System.IO.StreamReader.ReadBuffer()
   at System.IO.StreamReader.ReadToEnd()
   at OutSystems.RESTService.Formatters.TextMediaTypeFormatter.ReadFromStreamAsync(Type type, Stream readStream, HttpContent content, IFormatterLogger formatterLogger)
--- 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 System.Net.Http.HttpContentExtensions.<ReadAsAsyncCore>d__0`1.MoveNext()
--- 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 System.Web.Http.ModelBinding.FormatterParameterBinding.<ExecuteBindingAsyncCore>d__0.MoveNext()
--- 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 System.Web.Http.Controllers.HttpActionBinding.<ExecuteBindingAsyncCore>d__0.MoveNext()
--- 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 System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()
--- 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 System.Web.Http.Filters.AuthorizationFilterAttribute.<ExecuteAuthorizationFilterAsyncCore>d__2.MoveNext()
--- 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 System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext()





CommunicationException: The connection has timed out
    at XMLHttpRequest.g.ontimeout (https://tech-touch.randstad.co.jp/MySpot/scripts/OutSystems.js?WEXIMH3sR2i0DWyIJfctCA:3:8010)








I am getting there errors. Could someone please let me know what is this error about and how can we resolve this.

0
0
05 Mar 2019
2021-04-09 11-42-43
assif_tiger
Champion

Hi,

Increase the Server Request Timeout Value  for  Module under Properties

or

If it is a SOAP then you can set the timeout for particular request.


Perhaps the request is getting timeout & there is no way to resolve it... you can olny handle the exception or increase the timeout for the same.


thanks,

Assif

0
0
05 Mar 2019

We are getting the same issue and have increased all of our data fetch timeouts to 180. This has not resolved the issue. Any suggestions to resolve this issue would be greatly appreciated.

3
0
15 Oct 2021

Hi Michael, 

May I know if you have any steps done to resolve this issue? Thank you

0
0
04 Oct

Hello, we were able to fix it. We had data that we brought through Data Action, a list of texts and images from the OS tables.


The problem was the weight of the image that we brought, we changed them to images with a smaller weight and it was fixed. That error stopped appearing in Service Center.


I hope it helps you, greetings and good vibes

0
0
21 Nov
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.