Fatal error, will return 1. Java output Line=: 1 FATAL: Error in discovery : Exception=java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.CommunicationException [Login failed for an unknown reason: HTTP/1.1 404 Not Found]

Background

We were trying to Add Fusion Middleware SOA/Weblogic target inside Oracle Enterprise Cloud control 13c. Both components been deployed in Oracle Cloud Infrastructure using Market Place Image.

OEM Product Version: 13.5.0.19

SOA Suite 12.2.1.4

 As stated in below screen shot- 

 

but were hitting this Error message - 

Connecting with soamp-soa-0.spokedsoa.spokedvcn.oraclevcn.com:7001 weblogic ...... service:jmx:t3://soamp-sxxa-x.xxxxxsoa.sxxxxdxx.xxxxvxx.com:7001/jndi/weblogic.management.mbeanservers.domainruntime

sdk.discovery.discover.WeblogicDiscovery.discover debugging enabled.

sdk.discovery.discover.DiscoveryThread.setDiscoveryInputBeanBase enabling debugging

sdk.discovery.discover.DiscoveryThread.run In

sdk.discovery.discover.DiscoveryThread.discover In

sdk.discovery.discover.DiscoveryThread.discover In

sdk.discovery.discover.DiscoveryThread.run Out

sdk.discovery.discover.WeblogicDiscovery.discover Sleep Count = 1

sdk.discovery.discover.WeblogicDiscovery.discover Thread is not alive

sdk.discovery.discover.WeblogicDiscovery.discover getDiscoveredTargets

FATAL: Error in discovery : Exception=java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.CommunicationException [Login failed for an unknown reason: HTTP/1.1 404 Not Found]

java.lang.Exception: java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.CommunicationException [Login failed for an unknown reason: HTTP/1.1 404 Not Found]

We spent significant time to troubleshoot that error. MOS 1458357.1 helped up to some extent by enabling debug mode for emagent_perl.trc log file, also advising oracle_wls.pl scipt file which gets used to discover the target but still problem was not resolved. 

Until i found another blog talking about checking JMX service running or not within Weblogic Server. 

In order to search about JMX Server status, you need to check either your <domain>.log or AdminServer.log. Search this BEA code inside your log - 

cat soamp_adminserver.out | grep BEA-149512

In this we noticed that JMX Server actually using 9071 port vs we were using 7001 default WLS http port. 

The moment we changed from 7001 to 9071 port OEM was able to discover SOA Domain and pull out all target details. 

This document also state all default port of WLS and its purpose - https://docs.oracle.com/en/cloud/paas/weblogic-cloud/user/default-ports.html 

When I was searching for above erorr message couldn't find any useful blog detailing exact error. Hence, thought to publish this quick solution blog post. 

I hope that help. 

Happy blogging :)