Out of Memory - D6 RB10.04 XP
Hi
I occasionally get an Out of Memory error in the log and a dialog with the
following message
---------------------------
Reportserver
---------------------------
TrsServer - Fatal exception.
---------------------------
OK
---------------------------
The log from the same time shows
"20080229 12:56:18:553","Processing request for report
Reports\Documents\Itinerary EOutOfMemory, Out of
memory",seError,0,,,{46E4ECB2-4216-432C-912C-1B04157A86A8}
"20080229 12:56:18:631","Session
End",seInformation,0,,,{46E4ECB2-4216-432C-912C-1B04157A86A8}
"20080229 12:56:18:631","Out of memory",seError,0,,,
"20080229 12:56:18:631","Send page 1: Reports\Management\Consultants Stats
Report",seServiceResponse,5581,PublishReport,"Report
Publishing",{18793BBA-5CBB-48EE-B1B1-C9BF9DBC2333}
"20080229 12:56:18:631","Send page 1: Reports\Accounts\Daily Receipts and
Refunds by Transaction Date",seServiceResponse,8636,PublishReport,"Report
Publishing",{91C2DA5A-C198-4B7A-B552-C52E01997A24}
"20080229 12:56:19:100","Send page 2: Reports\Accounts\Daily Receipts and
Refunds by Transaction Date",seServiceResponse,2371,PublishReport,"Report
Publishing",{91C2DA5A-C198-4B7A-B552-C52E01997A24}
"20080229 12:56:19:147","RB Server Stopped",seInformation,0,,,
I then have to restart the server and all is well.
Any ideas. Is there something i should do with the server on a regular basis
to avoid this?
regards
I occasionally get an Out of Memory error in the log and a dialog with the
following message
---------------------------
Reportserver
---------------------------
TrsServer - Fatal exception.
---------------------------
OK
---------------------------
The log from the same time shows
"20080229 12:56:18:553","Processing request for report
Reports\Documents\Itinerary EOutOfMemory, Out of
memory",seError,0,,,{46E4ECB2-4216-432C-912C-1B04157A86A8}
"20080229 12:56:18:631","Session
End",seInformation,0,,,{46E4ECB2-4216-432C-912C-1B04157A86A8}
"20080229 12:56:18:631","Out of memory",seError,0,,,
"20080229 12:56:18:631","Send page 1: Reports\Management\Consultants Stats
Report",seServiceResponse,5581,PublishReport,"Report
Publishing",{18793BBA-5CBB-48EE-B1B1-C9BF9DBC2333}
"20080229 12:56:18:631","Send page 1: Reports\Accounts\Daily Receipts and
Refunds by Transaction Date",seServiceResponse,8636,PublishReport,"Report
Publishing",{91C2DA5A-C198-4B7A-B552-C52E01997A24}
"20080229 12:56:19:100","Send page 2: Reports\Accounts\Daily Receipts and
Refunds by Transaction Date",seServiceResponse,2371,PublishReport,"Report
Publishing",{91C2DA5A-C198-4B7A-B552-C52E01997A24}
"20080229 12:56:19:147","RB Server Stopped",seInformation,0,,,
I then have to restart the server and all is well.
Any ideas. Is there something i should do with the server on a regular basis
to avoid this?
regards
This discussion has been closed.
Comments
Run the reports using a tool that can check for memory/resource leaks.
Make sure you are not using the BDE. The BDE architecture is old and was
never designed to run in a multi-threaded/ server environment. Each session
requires the entire BDE to be loaded into memory another time - quickly
running out of memory. This is constrasts to other architectures which would
load a single time.
--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
I use ODAC and I will attempt to analyse the server although this issue
occurs rarely so it is subtle.
Great, just checking - the only time I have encountered Out Of Memory is
doing some testing that used the BDE.
Have not encountered that error with the demo server running on our web site
and we are not receiving feedback from other customers encountering Out Of
Memory errors.
--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
What happens once a report has been served to the client. Does the thread
get destoryed or is it left lying around to be used again?
I ask because this has happened again and I am noting a gradual memory
footprint for the server until it finally gives up. It is a heavily used
server and takes a week or so to cause an issue. Would using the service
wrapper help in this instance? Would it just restart the server.
Each client is assigned a SessionID. Sessions time out automatically - due
to inactivity. The TrsServer.TimeOut property 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.
When the Session is freed, then the report module associate with it is
free'd.
Try using ReportBuilder Services. If you run the server within the context
of ReportBuilder Services then it will try to restart the server in the
event of a crash. (There is no way to guarantee that it can successfully
restart the server, but it will try.)
--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com