+1-888-365-2779
Try Now
More in this section

Forums / Developing with Sitefinity / Stop Sending newsletter

Stop Sending newsletter

4 posts, 0 answered
  1. Flavio Cometto
    Flavio Cometto avatar
    14 posts
    Registered:
    17 Oct 2009
    26 Sep 2010
    Link to this post
    Hi all,
    we have a standard sitefinity 3.7 SP2 installed, since few day newsletter send process stop sending newsletter arbitrary after 50, 60 mails. Checking sitefinity log file when process stop sending (fails columns of sf_Notif_ProgressState set to 1), I have noticed a Request timed out. (Please find attached log)
    I did this checks:
    Server is responsive ( I have a virtualized server Windows Server 2008 R2 dedicated)
    Sending interval is set to 2000
    ping of application pool is set to 60 seconds

    Have you any suggestion?

    Thank you in advance
    Flavio


    9/26/2010 8:12:27 PM [UNKNOWN]
    ************************************************************************************
    ID: b0f185fb-be0f-49ba-92fc-fef38679505a; Code: 3001; Occurrence: 1; Sequence: 126
    ------------------------------------------------------------------------------------

    Application information:
     Machine name: ANARDIL
     OS Version: Microsoft Windows NT 6.1.7600.0
     Product Version: 3.7.2057.2
     Application Path: E:\WebSites\Clienti\web\IamaSource\www.iamasource.com\
     Debug: False

    Process information:
     Process ID: 3104
     Process Name: w3wp

    Request information:
     Request URL: /Sitefinity/Admin/Services/MailingWebService.asmx?WSDL
     Rewrite URL: http://www.iamasource.com/Sitefinity/Admin/Services/MailingWebService.asmx?WSDL
     Url Referrer:  Is Authenticated: True
     Authentication Type: Forms
     User: portalAdmin
     User Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.4952)
     User Address: 192.168.1.121

    Variables:
     c058d54d-4050-4be7-9307-6fb3940086ae: NHibernate.Burrow.Impl.WorkSpace
     WebServiceSoapVersion: Soap11
     RadControlRandomNumber: 0
     AspSessionIDManagerInitializeRequestCalled: True
     CmsHttpRequest: /Sitefinity/Admin/Services/MailingWebService.asmx?WSDL

    - L0 -------------------------------------------------------------------------------

    Exception Type: System.Web.HttpException

    Message: Request timed out.

    Source:

    Stack Trace:

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

  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    26 Sep 2010
    Link to this post
    Hello Flavio,

    Try increasing

    • executionTimeout
    • maxRequestLength

    Check whether the application pool  gets recycled due to some limits which will cause the same behavior. In our code the emails are sending on portions ( span -1 second).

    Best wishes,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Flavio Cometto
    Flavio Cometto avatar
    14 posts
    Registered:
    17 Oct 2009
    27 Sep 2010
    Link to this post
    Hi Ivan,
    thank You for faster anwser.
    This happens since migration from Windows 2003 server II6 to Windows 2008 R2 server II7.5 platform.
    After couple of search on forum I have found posts that seems related to default number of concurrent request (12) for asp.net 3.5 SP1 on appl pool in integrated mode . for examples:
    http://forums.asp.net/p/1277058/2430045.aspx
    http://blogs.x2line.com/al/archive/2010/01/04/3718.aspx
    http://boardreader.com/thread/Request_timed_out_errors_moving_from_II_9sfnXonrr.html

    So, I changed executionTimeout from default value to 3600 in order to check if anythings change, anyway it's sound strange because on IIS6 this value was set to default and worked fine (1500 newsletter subscribers has been sent correctly).

    Have You any other consideration about it?

    Regards.

    Flavio
  4. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    27 Sep 2010
    Link to this post
    Hi Flavio,

    Setting both the properties should fix this issue, otherwise your IIS server is timing out due to not enough memory or some other limits which Sitefinity does not control.

    All the best,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Register for webinar
4 posts, 0 answered