user75ponic user75ponic - 3 months ago 25
Java Question

Weblogic errors after getting deployed (published) : Error 503--Service Unavailable

I have a small web application where I am using Spring, Hibernate and JSF2.0.

I am deploying my application to Weblogic 10.3.6 which in integrated with Eclipse server. When I publish application to server, it gets published(deployed) however it takes quite some time to get published when compared to Glassfish.

The problem I am having is when I try to run application from browser I am getting the following error in browser, though I do not see any errors or exception in logs. How can I resolve this issue? And why it is taking so much to gets deployed to server?

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.


Go to the admin console, Check the status of your server, Check the status of the application itself that you were trying to deploy. Make sure its started and ready to take requests.

Regarding why its taking long to deploy, I think its down to using Eclipse itself IMO. When redeploying app's if you deploy some of the files as libraries then the deployment will be much more fasted. If you are trying to include all the libraries in your EAR file itself then the server will take longer.