The request channel timed out...

Posted by Community Admin on 04-Aug-2018 14:11

The request channel timed out...

All Replies

Posted by Community Admin on 21-Aug-2012 00:00

Site History:

This was a SF3.7sp4 site that was migrated to 5.1. User controls were rewritten to use the native and fluent apis. Windows 2003, IIS6

Issue:

When the publish' button on a page editor is pressed, the blue loading gif plays for one minute, then a popup is shown with the following

message: "The request channel timed out while waiting for a reply after 00:01:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout." See attached screenshot.

The message appears after one minute.

Templates can be saved, this behaviour only affects publishing pages.

This timeout does not generate any entries in the IIS error log. The error entry in the SF error log is as follows:

Category: ErrorLog

Priority: 0

EventId: 90000

Severity: Error

Title:Enterprise Library Exception Handling

Machine: SERVERNAME

App Domain: /LM/W3SVC/1441573237/Root-11-129899689643305351

ProcessId: 5016

Process Name: c:\windows\system32\inetsrv\w3wp.exe

Thread Name:

Win32 ThreadId:6484

Extended Properties:

----------------------------------------

----------------------------------------

Timestamp: 21/08/2012 12:25:42

Message: HandlingInstanceID: 3c55d2c1-8d7c-451c-8bda-42ea38e4c86f

An exception of type 'System.TimeoutException' occurred and was caught.

-----------------------------------------------------------------------

08/21/2012 08:25:42

Type : System.TimeoutException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Message : The request channel timed out while waiting for a reply after 00:01:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.

Source : mscorlib

Help link :

Data : System.Collections.ListDictionaryInternal

TargetSite : Void

HandleReturnMessage(System.Runtime.Remoting.Messaging.IMessage,

System.Runtime.Remoting.Messaging.IMessage)

Stack Trace :

Server stack trace:

   at System.ServiceModel.Channels.RequestChannel.Request(Message

message, TimeSpan timeout)

   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message

message, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage

methodCall, ProxyOperationRuntime operation)

   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage

reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&

msgData, Int32 type)

   at Telerik.Sitefinity.ContentWorkflows.IService.SendMessage(String

operationName, Boolean isCheckedOut, Guid workflowDefinitionId, Guid contentId, String providerName, Dictionary`2 contextBag)

   at Telerik.Sitefinity.Workflow.WorkflowManager.MessageWorkflow(String

wokflowUrl, String operationName, WorkflowDefinition workflowDefinition, Guid contentId, String providerName, Boolean isCheckedOut, Dictionary`2 contextBag)

   at Telerik.Sitefinity.Workflow.WorkflowManager.MessageWorkflow(Guid

itemId, Type itemType, String providerName, String operationName, Boolean isCheckedOut, Dictionary`2 contextBag)

   at Telerik.Sitefinity.Workflow.Services.WorkflowService.MessageWorkflowInternal(KeyValuePair`2[]

contextBag, String itemId, String itemType, String providerName, String workflowOperation)

   at Telerik.Sitefinity.Workflow.Services.WorkflowService.MessageWorkflow(KeyValuePair`2[]

contextBag, String itemId, String itemType, String providerName, String workflowOperation)

   at SyncInvokeMessageWorkflow(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object

instance, Object[] inputs, Object[]& outputs)

   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc&

rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc&

rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc&

rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc&

rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc&

rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc&

rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc&

rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc&

rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc&

rpc)

   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean

isOperationContextSet)

Additional Info:

MachineName : SERVERNAME

TimeStamp : 21/08/2012 12:25:42

FullName : Telerik.Sitefinity.Utilities, Version=5.1.3270.0, Culture=neutral, PublicKeyToken=b28c218413bdf563 AppDomainName : /LM/W3SVC/1441573237/Root-11-129899689643305351

ThreadIdentity :

WindowsIdentity : NT AUTHORITY\NETWORK SERVICE Requested URL :

http://siteurl/Sitefinity/Services/Workflow/WorkflowService.svc/MessageWorkflow/4b150c7f-4a7f-4286-a7d8-d168dd7ac02f/?itemType=Telerik.Sitefinity.Pages.Model.PageNode&workflowOperation=Publish

                Inner Exception

                ---------------

                Type : System.TimeoutException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

                Message : The HTTP request to

'siteurl/.../PagesApprovalWorkflow.xamlx'

has exceeded the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout.

                Source : System.ServiceModel

                Help link :

                Data : System.Collections.ListDictionaryInternal

                TargetSite : System.Net.HttpWebResponse ProcessGetResponseWebException(System.Net.WebException,

System.Net.HttpWebRequest,

System.ServiceModel.Channels.HttpAbortReason)

                Stack Trace :    at

System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException

webException, HttpWebRequest request, HttpAbortReason abortReason)

                   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan

timeout)

                   at System.ServiceModel.Channels.RequestChannel.Request(Message

message, TimeSpan timeout)

                                Inner Exception

                                ---------------

                                Type : System.Net.WebException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

                                Message : The operation has timed out

                                Source : System

                                Help link :

                                Status : Timeout

                                Response :

                                Data : System.Collections.ListDictionaryInternal

                                TargetSite : System.Net.WebResponse GetResponse()

                                Stack Trace :    at System.Net.HttpWebRequest.GetResponse()

                                   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan

timeout)

I've followed the directions on the KB, here:

http://www.sitefinity.com/devnet/kb/sitefinity-5-x/when-publishing-or-saving-a-page-you-are-getting-a-timeout-message-for-the-request-channel-of-waiting-for-response-for-some-time.aspx

The following is the basicHttpBinding from the web.config:

<system.serviceModel>

    <bindings>

      <basicHttpBinding>

        <binding name="basicHttpBinding"

maxReceivedMessageSize="2147483647" maxBufferSize="2147483647"

sendTimeout="15:10:00">

          <security mode="None" />

        </binding>

Despite this addition, the timeout message still appears after one minute. Any help would be appreciated.

Posted by Community Admin on 13-Sep-2012 00:00

Hi,

It appears that the service is timing out which is most probably due to the server connection or because of the load on the site. You can try and increase the SendTimeout value on the binding as shown bellow ( you can customize the values so they match your situation ):

<bindings>
      <basicHttpBinding>
        <bindingname="basicHttpBinding"maxReceivedMessageSize="2147483647"maxBufferSize="2147483647"sendTimeout="01:10:00">
          <securitymode="None"/>
        </binding>
      </basicHttpBinding>
    </bindings>

Additionally, please review the following forum posts:
http://www.sitefinity.com/devnet/forums/sitefinity/bugs-issues/unable-to-publish-anything-after-upgrade-to-4-2-sp1-1733.aspx
http://www.sitefinity.com/devnet/forums/sitefinity/bugs-issues/help-5-1-errors-when-saving-anything-i-e-news-item-page-et-cetera.aspx

Also there is a very good article about improving performance of IIS sites - http://blogs.msdn.com/b/flo/archive/2008/06/17/easy-wins-tuning-the-performance-of-a-web-site.aspx - there are some directions on how to improve WCF performance.

Kind regards,
Stefani Tacheva
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

Posted by Community Admin on 21-Oct-2013 00:00
Posted by Community Admin on 24-Oct-2013 00:00

Hi,

Thank you Markus for sharing the KB article. The problem might also be caused by a bug in the search index in version Sitefinity 5.x and 6.0 which has been fixed in Sitefinity 6.1.

Regards,
Stefani Tacheva
Telerik

Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

Posted by Community Admin on 24-Oct-2013 00:00

Hello,

Thank you Markus for sharing the KB article. The problem might also be caused by a bug in the search index in version Sitefinity 5.x and 6.0 which has been fixed in Sitefinity 6.1.

Regards,
Stefani Tacheva
Telerik

Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

This thread is closed