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

Exception Handling in Report Server

edited October 2003 in Server
I've been doing some stress testing on my RB Server setup by having three
web clients simultaneously running report after report.

Occasionally, I get a ESocket Error "Connection Timed Out" on the server.
The next thing that happens is the dreaded TrsServer - Fatal Exception,
which also happens when I raise exceptions in events such as
TrsReportTemplateVolume.OnGetDirectory.

After a "Fatal Exception", the report server is dead as a doornail and has
to be restarted. Is there any way to change the way these exceptions are
handed so that they only affect the current report and/or session and don't
bring down the whole server?

--
Nathan Sutcliffe
nsutcliffe at speedlinesolutions period com

Comments

  • edited October 2003

    Either raise EReportBuilderError, one its descendants, or create your own
    descendants. The the exception will be passed to the client and raised
    there. And the server will only kill the request - there will not be a fatal
    error.

    EReportBuilderError and its descendants are defined in ppTypes. Open
    RBuilder\Source\ppTypes and search for EReportBuilderError.




    --
    Nard Moseley
    Digital Metaphors
    http://www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited October 2003
    > Either raise EReportBuilderError, one its descendants, or create your own
    fatal


    That's a whole lot better - thanks!

    --
    Nathan Sutcliffe
    nsutcliffe at speedlinesolutions period com
This discussion has been closed.