Oracle Apps DBA: Keeping E-Business Suite Alive · Module 10 · WebLogic and the technology stack
Reading a WebLogic log
Lesson 105 of 184 · 2 min
A different format, a different vocabulary, and THE TWO OR THREE MESSAGES THAT ACTUALLY MEAN SOMETHING. A WebLogic log looks nothing like a database alert log and it is far noisier, which is why people give up on it. Long Java stack traces, severities that do not mean what they say, and a great deal of routine chatter. THE FIRST THING TO KNOW IS THAT SEVERITY IS UNRELIABLE. Warnings appear constantly on a completely healthy system, and something genuinely serious can be logged at a level that does not stand out. Filtering by severity alone produces either everything or nothing — so use TIME as the primary filter: what appeared around the moment the symptom started. THE SECOND IS THAT A STACK TRACE IS READ AT ITS ENDS, NOT ITS MIDDLE. The top line names the exception, which is often generic; the useful part is the CAUSED BY at the…
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