Why get this "System.InvalidOperationException: Timeouts are not supported on this thread" inconsistently

I am getting "System.InvalidOperationException: Timeouts are not supported on this thread" when loading hotlist data from a web service. Plz find below exception log trace for the same.

[2014-12-09 09: 38: 10.4402] Info: 0033216: <-Get Hot List Started () [2014-12-09 09: 38: 33.9415] Error: 0033217: System.InvalidOperationException: Timeouts are not supported on this thread ...

Server Stack Trace: at System.IO.Stream.get_ReadTimeout () at System.ServiceModel.Channels.HttpChannelUtilities.CreateResponseWebException (WebException webException, response HttpWebResponse) on System.ServiceModel.Channputels.Httpponse , Int32 offset, Int32 count) when System.ServiceModel.Channels.MessageEncoder.BufferMessageStream (Stream stream, BufferManager bufferManager, Int32 maxBufferSize) when System.ServiceModel.Channels.MessageEncoder.ReadMessage (stream stream, BufferMessage) at System.ServiceModel.Channels.HttpInput.ReadChunkedBufferedMessage (Stream inputStream) at System.ServiceModel.Channels.HttpInput.ParseIncomingMessage (HttpRequestMessage httpRequestMessage, Exception & requestException) at System.ServiceMessage.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply (TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request (message message, TimeSpanel timeout) on System.ServiceModel.Channels.RequestChannel.Request (message message, TimeSpanel timeout) on System.ServiceModel.Channels.RequestChannel.Request (message message, TimeSpanel timeout) on System.ServiceModel.Channels.RequestChannel.Request (message message, TimeSpanel timeout) on System.ServiceModel.Channels.RequestChannel.Request (message message, TimeSpanel. TimeSpan out) to System.ServiceModel.Channels.ServiceChannel.Call (String action, Boolean oneway, ProxyOperationRuntime operation, Object [] ins, Object [], TimeSpan timeout) to System.ServiceModel.Channels.ServiceChannelProxy.InvokeService (IMethodCallage , ProxyOperationRuntime) when System.ServiceModel.Channels.ServiceChannelProxy.Invoke (Izzade message)ServiceModel.Dispatcher.RequestChannelBinder.Request (Message message, TimeSpan timeout) on System.ServiceModel.Channels.ServiceChannel.Call (String action, Boolean oneway, ProxyOperationRuntime operation, Object [] ins, Object [], TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService (IMethodCallMessage methodCall, ProxyOperationRuntime) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke (Izzade message)ServiceModel.Dispatcher.RequestChannelBinder.Request (Message message, TimeSpan timeout) on System.ServiceModel.Channels.ServiceChannel.Call (String action, Boolean oneway, ProxyOperationRuntime operation, Object [] ins, Object [], TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService (IMethodCallMessage methodCall, ProxyOperationRuntime) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke (Izzade message)Invoke (Izzade message)Invoke (Izzade message)

Exception thrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage (Izzade reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (MessageData & msgData, type. Integration.Proxy.Reference.ReferenceWebService.getHotlist (getHotlistRequest request) at DMS.Integration.Proxy.Reference.ReferenceWebServiceClient.DMS.Integration.Proxy.Reference.ReferenceWebService.getHotlist (getHotlist.Request. Request) at DMS. getHotlist (getHotlist getHotlist1) at DMS.Services.HotListServiceProxy.GetHotList () at DMS.GUI.Utils.AddToHotListHelper.b__5 () at DMS.Lib.Base.ServiceProxyWrapper`1.Execute () [2014-12-09 : 33.9415] Error: 0033218: System.ApplicationException: getHotList

[2014-12-09 09: 38: 33.9415] Info: 0033219: Service call time, 94835ms, Action: getHotList

I can confirm that we are not doing any memory stream operations when we get the hotlist.

Below are the bindings for the service in app.config:

 <bindings>
        <basicHttpBinding>
            <binding name="basicBinding" maxBufferSize="209715200" maxReceivedMessageSize="209715200">
                <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647"
                    maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />
                <security mode="TransportCredentialOnly">
                    <transport clientCredentialType="Basic"/>
                </security>
            </binding>
        </basicHttpBinding>
    </bindings>

      

Investigated in a QA environment, and the application is installed on the server and by connecting to the VPN, they can access the application for testing.

+3


source to share





All Articles