I would personally start looking at as many log files as you
can, not just the application that has bombed out. Look at the OS logs
if you can and see what other processes were running, was a database being hit
real hard at the time.....
There are lots of different combinations of things that could
have happened.
Get friendly with the sysadmin, unless you are the sysadmin, and
see what is going on under the bonnet.
Regards
Jason Bell
----- Original Message -----
Sent: Thursday, October 09, 2003 9:50
AM
Subject: [jdjlist] No stack trace for
OutOfMemoryError
We are getting
OutOfMemoryErrors in our app but there is no stack trace. At the time
the Throwable is printed it seems to have sufficient memory (because it opens
a file, prints other info, etc). Does anyone have any ideas why there is no
stack trace? Is it because there isn't sufficient memory to fill the
stack trace when if is created?
Running 1.4.0 on JRun 2.3.3
with 768MB RAM for Java (min and max) an using SoftReferences for soft
caches.
James Stauffer
---
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
--- 