Home Server
New Blog Posts: Merging Reports - Part 1 and Part 2

Report Timeouts

edited April 2006 in Server
Hello

What is the best way to prevent connection timeouts when running reports
that take a while to generate?

I am using Report Builder Server

If I modify the Timeout property on the rsServer component at run time will
this increase the timeout for all reports or just the one that I am doing?

Do I need to do anything on the web tier?

Cheers

Paul

Comments

  • edited April 2006

    If you are using ADO, then you can use the ADOConnection.CommandTimeOut
    property to control the database connection time out.




    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited April 2006
    Hi Nard

    Is there no other way?

    I use ADO but perform several queries many times, running the queries once
    does not take long, its the fact that in order to generate my report I have
    to run the queries in one case 1000 times - I get all invoivrs for 1
    location, then the next loccation,etc

    Cheers

    PAul

  • edited April 2006
    Hi Nard

    Just to clarify, I am talking about the Server Timeout at the client, not
    database connection timeout

    Cheers

    Paul

  • edited April 2006


    Ok, I misunderstood.

    Here is a list of relevant properties and their defintions from the online
    help file. Hope this helps...


    1. WebTier.ServerConnection.TimeOut

    The number of seconds to wait for a server response before timing out.

    (This is probably the most relevant to your question. The client sends a
    request to the server and then waits for a response. If not response is
    receive from the server after X seconds then the client times out)

    2. WebTier.SessionOptions.SessionTimeOut

    Defaults to 300 seconds (five minutes.). Use SessionTimeout to specify the
    number of seconds that a session can remain inactive until it expires.
    Expired sessions are deleted by the web tier garbage collector.

    (This is the session between the web browser and the webtier).

    3. Server.TimeOut

    Specifies the time, in seconds, that a session can remain open on the server
    without receiving a client request. If a session is idle for TimeOut seconds
    then the session will be freed by the server. If the server receives
    additional requests from the client for the session, a new session will be
    created and the appropriate response returned.


    (This is the session between the webtier and the report server).

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.