Wednesday, January 27, 2016

Error 503--Service Unavailable when trying to access the EM console

Problem:

If you're running Oracle Fusion Middleware (specifically Oracle SOA Suite 11g), and when navigating to the EM console via this URL:
http://soadev.raastech.com:7001/em
We get this error on the browser:
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.


Solution:

In this particular case, the file targets.xml was missing.

1. Confirm that targets.xml is missing.
export DOMAIN_HOME=/u01/app/oracle/middleware/user_projects/domains/soa_domain 
ls -l $DOMAIN_HOME/sysman/state/targets.xml

2. If so, recreate the targets.xml file using the following as a template:
<Targets>
 <Target TYPE="oracle_ias_farm" NAME="Farm_soa_domain" DISPLAY_NAME="Farm_soa_domain"> 
  <Property NAME="MachineName" VALUE="soadev.raastech.com"/> 
  <Property NAME="Port" VALUE="7001"/> 
  <Property NAME="isLocal" VALUE="true"/> 
  <Property NAME="Protocol" VALUE="t3"/> 
  <Property NAME="serviceURL" VALUE="service:jmx:t3://soadev.raastech.com:7001/jndi/weblogic.management.mbeanservers.domainruntime"/> 
  <Property NAME="WebLogicHome" VALUE="/u01/app/oracle/middleware/wlserver_10.3"/>
  <Property NAME="DomainHome" VALUE="/u01/app/oracle/middleware/user_projects/domains/soa_domain"/>
 </Target> 
</Targets>

3. Restart the AdminServer


Applicable Versions:
  • Oracle SOA Suite 11g (11.1.1.x)


2 comments:

Anonymous said...

Yup .. It helped to me too .. target.xml was missing from one node so whenever AdminServer was started on that node ... I was getting Error 503 while accesing em .

After reading this post I copied target.xml from other node , edited hostname and restarted Admin Server and It started working .

Thanks for this Post.

Best Regards

Anonymous said...

You rock!

Thanks a lot.