Friday, June 20, 2008

WebLogic Server 10 : 503--Service Unavailable

"

Error 503--Service Unavailable
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.4 503 Service Unavailable

The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.

"

I hit this error after deploying an application & trying out the URL for my JSP.

I have primarily worked on OC4J & expected that the steps would be pretty much the same. However, I hit this bug & was scracthing my head for quite sometime - until I realized it.

The Application has to be started after the deployment.

The application is not started by default ( as in OC4J ) & thus, was unavailable to service the requests.

I am just posting this for future reference to newcomers like me.

No comments: