How to Diagnose and Debug a HTTP 503 Error in a Portal Environment
(Doc ID 751101.1)
Last updated on JULY 08, 2019
Applies to:Portal - Version 10.1.2.0.2 to 10.1.4.2 [Release 10gR2]
Information in this document applies to any platform.
The purpose of this document is to give some guidance when Users or Systems Administrators encounter HTTP 503 errors.
HTTP 503 is the standard HTTP error that means "Service Unavailable."
503 error is a generic error which can be caused by many situations.
A 503 error can be displayed in any or all of the following locations:-
- Web Cache Event Log
- Apache Error Log
- OC4J application.log
A root cause error may be displayed with the 503 which will be more helpful in determining exactly what the issue might be.
A 503 may not cause any obvious user error, or might be simply resolved by a browser refresh. It can be a temporary issue or a permanent problem.
For these reasons finding the root cause can be extremely difficult.
There are a number of notes written about different types of 503 errors which may be encountered. This note aims to act as a Master Note to finding the possible reasons for your particular situation.
Examples of where a 503 error may occur
Apache error log errors
eg <Midtier Oracle Home>/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1/application.log
<TITLE>503 Service Temporarily Unavailable</TITLE>
<H1>Service Temporarily Unavailable</H1>
The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.
<ADDRESS>Oracle-Application-Server-10g/10.1.2.0.0 Oracle-HTTP-Server Server at my.host.com Port 7778</ADDRESS>
Note: If the debugging level in the PPE is not high, then a 503 error may not actually be displayed in any logs. Instead the error seen might just be a "Stall timeout reached". Increase the debug level to see if a 503 is actually being generated.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Examples of where a 503 error may occur|
|Questions and Answers|
|HOW TO START DEBUGGING THE ERROR|
|Step 1 - Find All Reported Errors|
|Step 2 - Search Knowledge Base For Similar Issues|
|Step 3 - Apply Solutions From Any Relevant Knowledge Base Notes|
|Step 4 - Determine in which layer the error originated|
|Step 5 - Raise A Service Request|
|NOTES SORTED BY CATEGORY OF ERROR|
|Unable to Access Portal At All|
|Relating To Database Portlets|
|Relating To Java Portlets|
|SSO protected JSPs|