db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Fischer <tfisc...@apache.org>
Subject Re: java.lang.OutOfMemoryError
Date Sat, 30 Dec 2006 10:09:20 GMT
An out of memory error is typically very difficult to pinpoint. The place 
where this error occurs is typically not connected to the place where the 
problem sits. Personally, I know of two ways of dealing with this
- you can have an idea what happens. The answers before have provided 
situations where OutOfMemory-Problems typically happen.
- If you think that none of the typical causes apply to you, you have to 
find out the hard way. To get an idea of the cause of the problem, create 
a heap dump of the virtual machine just after an OutOfMemory-Error occured 
(on linux, this is done by using the "kill -3" command on the appropriate 
process). Then, scan through the heap dump to see which objects occur most 
often. These are usually the objects which are not dereferenced and cause 
the memory overflow. Then go through the code and find out where these 
objects are created, and why they are not thrown away after being used.
You might need more information out of the heap dump than just the class 
names of the relevant object; there are tools showing the refences out of 
heap dumps but I never used one myself.

    Hope this helps,

          Thomas

On Mon, 18 Dec 2006, jill han wrote:

> What could cause java.lang.OutOfMemoryError ?
> The application is built on turbine/torque/velocity.
>
> Thanks in advance
>
> Jill
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org


Mime
View raw message