503 Service Unavailable

adityan20 · ‎11-26-2009

Hi All,

We have this exception when we are trying to read a property. But this connection is active and working for other entities, only with this entity how are we having Service unavailable exception. When does service unavialable exceptions occur.

Please let me know if any one had this similar issue.

ERROR 11/26 03:30:23 Stderr 700100 AxisFault

faultCode: HTTP

faultSubcode:

faultString: (503)Service Unavailable

faultActor:

faultNode:

faultDetail:

{}:return code: 503

<HTML><BODY><H1>503 Service Unavailable</H1></BODY></HTML>

HttpErrorCode:503

ERROR 11/26 03:30:23 Stderr 700100 (503)Service Unavailable

ERROR 11/26 03:30:23 Stderr 700100 at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744)

ERROR 11/26 03:30:23 Stderr 700100 at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)

ERROR 11/26 03:30:23 Stderr 700100 at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)

ERROR 11/26 03:30:23 Stderr 700100 at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)

ERROR 11/26 03:30:23 Stderr 700100 at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)

ERROR 11/26 03:30:23 Stderr 700100 at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)

ERROR 11/26 03:30:23 Stderr 700100 at org.apache.axis.client.Call.invokeEngine(Call.java:2784)

ERROR 11/26 03:30:23 Stderr 700100 at org.apache.axis.client.Call.invoke(Call.java:2767)

ERROR 11/26 03:30:23 Stderr 700100 at org.apache.axis.client.Call.invoke(Call.java:2443)

ERROR 11/26 03:30:23 Stderr 700100 at org.apache.axis.client.Call.invoke(Call.java:2366)

ERROR 11/26 03:30:23 Stderr 700100 at org.apache.axis.client.Call.invoke(Call.java:1812)

ERROR 11/26 03:30:23 Stderr 700100 at com.vmware.vim25.VimBindingStub.retrieveProperties(VimBindingStub.java:26671)

muthumia · ‎03-02-2010

Same exception occurs @ our environment. what could be the problem? Does anybody have solution for this?

Thanks in advance.

sumwatwsted · ‎04-02-2011

I realize that this was created over a year ago but I'd like to help out as much as possible.

We were seeing similar errors in our DR environment until I uninstalled GoToMYPC on our vCenter server. It's completely understood that GoToMYPC uses 80/443 and we all know how sensitive vCenter 2.5 and newer can be to those exact ports, however, the interesting point I'm trying to make is that GoToMYPC had been installed on our vCenter server for years, even when it was a Windows 2003 box and we were on a much earlier version of vCenter.

My theory is that vSphere 4.x is even more sensitive than ever when it comes to ports 80/443/503, and after upgrading to vSphere 4.1 U1, this problem showed up.

So to sum up, check for GoToMYPC or any other 3rd party software that may use those ports and remove them.

Cheers.

rManic · ‎04-02-2011

following my help you

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1010041&sl... 0 171673825

regards

Manick

Regards Manic