Starting, stopping and the order

The sequence, THE TIME EACH STEP REALLY TAKES, and how to tell A SLOW START FROM A FAILED ONE. The order is fixed: database first, then the admin server, then the managed servers, then the web layer. Each depends on what precedes it, and starting out of order produces failures that name the wrong component — Module 4 Lesson 2's rule, one layer down. THE TIMING IS THE PART THIS LESSON EXISTS FOR, BECAUSE A JAVA APPLICATION SERVER STARTS SLOWLY AND SILENTLY. A managed server can take several minutes before it accepts a request, and for most of that time it is doing exactly what it should while producing almost nothing to look at. SO THE COMMONEST MISTAKE IN THIS MODULE IS RESTARTING SOMETHING THAT WAS STARTING FINE. Two minutes in, nothing responds, so somebody restarts it — and the clock goes back to zero. Repeat twice and a five-minute…

In this module: Module 10 · WebLogic and the technology stack

1. 1What sits between the user and EBS
2. 2The admin server and the managed servers
3. 3Starting, stopping and the order
4. 4Reading a WebLogic log
5. 5Memory, and the server that keeps restarting
6. 6Certificates and HTTPS
7. 7Java versions and the technology stack
8. 8The load balancer, and who owns it
9. 9What breaks: three technology stack failures
10. 10Lab briefing · Follow one request all the way down