Oracle Apps DBA: Keeping E-Business Suite Alive · Module 10 · WebLogic and the technology stack
Memory, and the server that keeps restarting
Lesson 106 of 184 · 2 min
Heap, out-of-memory failures, and THE DISTINCTION BETWEEN A LEAK AND AN UNDERSIZED SERVER. A Java server runs inside a fixed memory allocation, and when it cannot fit it fails — sometimes gracefully, often not. The symptom is a managed server that restarts by itself, repeatedly, and Lesson 9's second failure is a month of exactly that. THE DISTINCTION IN THE TITLE DECIDES THE FIX AND THE TWO LOOK IDENTICAL FROM THE OUTSIDE. AN UNDERSIZED SERVER RUNS OUT UNDER LOAD AND IS FINE OTHERWISE. Memory use rises during the busy period, hits the ceiling, and the server fails — and after a restart it is comfortable again. It correlates with load: month end, a heavy report, a busy morning. The fix is more memory, or less work on that server. A LEAK RISES REGARDLESS OF LOAD AND NEVER COMES BACK DOWN. Memory climbs steadily, quiet periods included, until the ceiling is…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, with a certificate on completion and a fourteen-day refund window.
In this module: Module 10 · WebLogic and the technology stack
- 1What sits between the user and EBS
- 2The admin server and the managed servers
- 3Starting, stopping and the order
- 4Reading a WebLogic log
- 5Memory, and the server that keeps restarting
- 6Certificates and HTTPS
- 7Java versions and the technology stack
- 8The load balancer, and who owns it
- 9What breaks: three technology stack failures
- 10Lab briefing · Follow one request all the way down