• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Application out of heap space : restart application or restart application server ?

Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Got this running application server on which runs... applications. Now one of them runs out of memory (see trace below).

2011-02-08 04:55:20,286|ERROR|
***snip snip***
java.lang.OutOfMemoryError: Java heap space

The approach we have now when it happens : is to shutdown the server through the Admin console and restart the server again.
admin console -> domain -> environment -> servers (shutdown, start)

As this is a live system at our customers site, we cannot experiment with it, but should it not be possible to just do a restart of the deployment
admin console -> domain -> deployments (stop, start)
Ranch Hand
Posts: 98
Oracle Redhat
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Just doing a server re-start might not be a permanent solution to the out of memory issues. You need to go to the root cause of it.

java.lang.OutOfMemoryError: Java heap space

This error indicates that there is no enough heap space available for the creation of the Java Objects.

There could be many reasons causing this situation.
1. If the application is generating more objects (consuming more heap space) than the one allocated one.
2. If the application is not releasing the resources associated with the objects even after a Garbage Collection. This situation is called Memory leak.

For different types of Out Of Memory issues refer the below link.


In both the case, you might need to profile your application so that you can get to the root cause of the issue and avoid any discrepancies in the production environment.

Note: Profiling tools would consume extra resources.

There are many profiles tools available for troubleshooting Out Of Memory related issues. Profiler tools like JProfiler, YouKit etc can be used.

Below link shows how JProfile can be used with WebLogic Server.


Below link shows how YourKit profiler tool can be used with WebLogic Server.


    Bookmark Topic Watch Topic
  • New Topic