If the memory increases very quickly then it is a coding issue that is
being exposed by a database connectivity problem.
To fix this:
Find all your code that loops through a recordset loop and change it such
as the example below. Depending on how exactly you've written your loops
you want to change it to exit the loop if there is an error.
Old Code:
While Not recordset.EOF
'Your code does something here
recordset.MoveNext
Wend
New Code:
While Not recordset.EOF and Err.Number = 0
'Your code does something here
recordset.MoveNext
Wend
You could also add some error logging to find out the exact nature of the
connectivity problem.
<%
'ErrorLog.inc
If Err.Number <> 0 Then
RecordError(_
Request.ServerVariables("SCRIPT_NAME") & ":" & _
Err.Number & ":" & _
Err.Description & ":" & _
Err.Source)
End If
Sub RecordError(WhatToWrite)
On Error Resume Next
Const ForAppending = 8
Dim fso, outputFile
Set fso = Server.CreateObject("Scripting.FileSystemObject")
Set outputFile = fso.OpenTextFile("c:\CustomLog.txt", ForAppending, True)
outputFile.WriteLine WhatToWrite
outputFile.Close
Set outputFile = Nothing
Set fso = Nothing
On Error GoTo 0
End Sub
%>
Hope this helps,
Brian Murphy-Booth<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: IIS 5, DLLHOST and Oracle