View Single Post
  #8 (permalink)  
Old December 7th, 2007, 16:49
miks miks is offline
Junior Member
 
Join Date: May 2007
Posts: 19
Thanks: 1
Thanked 2 Times in 2 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 0
miks is on a distinguished road
Re: Throwing OutOfMemory: allocLargeArray - Object size: 5766688, Num elements: 28833

Typically, with out of memory errors, the root cause of the problem come in lines 6 & 7 in the error. You should try to correlate those errors with a business user who is generating the error. In other words, reproduce the problem. Once you do, setup a web conf with support to show them what is causing it.

Some of problems are caused by the application attempting to allocate more memory than it needs. (IOW an OTM BUG ) You can see in the memory errors that it is doubling at some point, which is not a good sign.

You have plenty of memory to run the app.

lines 6 & 7:

at glog.server.producer.ProducerXML.toXML(ProducerXML .java:73)
at glog.webserver.util.Producer.createMasterElementRe mote(Producer.java:159)
Reply With Quote