This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
We are deploying our application on Oracle10g AS , version 10.1.3. Very frequently we get OutOfMemory error even for a single user. We are using the default settings for Java Options. Please suggest a solution ASAP.
When you create an application in OAS 10.1.3.x.x you can create a deployment file (see the help documentation in the IDE for the specific steps to create the deployment file). In the deployment file wizard, there is a drop down menu that allows you to set the max memory footprint for your application.
Also, you need to check the size of memory on the server that you are deploying to.
Thirdly, are you using any type of technology that is trying to pre-load a ton of objects (EJB, Spring Ioc, Servlets etc.)?
Even though Java "doesn't have memory leaks", it does if tons of objects are created and the reference to those objects are not released.
Did you use ADF to create the application? An app based on ADF may be trying to load a lot of database objects on start-up (ADF loves EJB).
I hope I am sending you in the right direction. Let me know how things go.