View Single Post
  #2 (permalink)  
Old March 7th, 2008, 15:46
chrisplough's Avatar
chrisplough chrisplough is offline
Site Moderator
 
Join Date: Jun 2006
Location: West Chester, PA
Posts: 847
Blog Entries: 7
Thanks: 53
Thanked 205 Times in 124 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 10
chrisplough has a spectacular aura aboutchrisplough has a spectacular aura aboutchrisplough has a spectacular aura about
Send a message via AIM to chrisplough
Re: Oracle Application Server running out of memory

JayVal,

The biggest issue is that you don't have enough memory allocated to the OTM App server. Allocating 1GB is the bare minimum for OTM and doesn't leave enough room for memory-intensive OTM processes.

If you're running on Win32, then you'll be limited to 1.2 or 1.4GB, but if you're running on any other platform, you should bump up to 2GB. This is done within your $OTM_HOME/oas/bin/oc4j.sh script.

Keep in mind that you'll need enough physical memory on your server to accommodate a heap of this size. If you're only running OAS on this server, and the heap is 2GB, then you should have 4GB of physical memory to allow room for the heap, Java native memory and OS. If you're running more, then you'll need more memory.

Hope this helps!

--Chris
__________________
Chris Plough
MavenWire

www.MavenWire.com
Reply With Quote