Posted 28 February 2022, 6:26 am EST
I am seeing an issue where the report run time exceeds the asp.net request timeout.
We are running 2 pairs of webservers with load balancing between each pair.
The issue seems to happen on one or two of the servers for a few minutes, then it straightens out.
I put code in to determine if the issue was between the webserver and the database. That was not the issue.
Here’s the code behind the page:
Using mStream As New MemoryStream
Using pdf As New PdfExport
pdf.Version = PdfVersion.Pdf17
pdf.Security.Permissions = PdfPermissions.AllowPrint
pdf.Security.Encrypt = True
pdf.Security.Use128Bit = True
pdf.Security.OwnerPassword = Guid.NewGuid.ToString
Dim rptStart As Date = Date.Now
Dim rpt As New Af469
rpt.SetData(dtAf469, False)
rpt.Run(False)
Dim rptEnd As Date = Date.Now
_rptTs = rptEnd.Subtract(rptStart)
_responseStart = Date.Now
mStream.Position = 0
Response.ContentType = “application/pdf”
Response.AddHeader(“content-disposition”, “inline; filename=AF469.PDF”)
pdf.Export(rpt.Document, mStream)
Response.BinaryWrite(mStream.ToArray())
Response.Flush()
rpt.Document.Dispose()
rpt.Dispose()
End Using
End Using
The timespan between rptStart and rptEnd will exceed 80,000 milliseconds on many of the error log entries.
Any ideas on how I can narrow down the cause for this issue?
