sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

In Enterprise Manager 12c Cloud Control the EM Console Service may show as DOWN if custom SSL certs being used are not imported to beacon agent.

You may see errors as below when running service test.

sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

You can either:

i) Import SSL certs to beacon agent OR

ii) Disable SSL & test:  

Login to the Cloud Control Console >> Targets >> Services >> Click Service >> Click "Monitoring Configuration" Tab >> Click "Service Tests and Beacons" >> Click Edit >> Click Tab "Advanced Properties"


Change the Validation "Authenticate SSL Certificates" to No.

How to check Oracle HTTP Server (OHS) component version?

How to check Oracle HTTP Server (OHS) component version?

Below are a couple of ways to check with Oracle HTTP Server (OHS) version used. There may be more ways to check it.

1) Go to $OHS_HOME/bin

Run ./httpd -version

It should return result as below based on the version of OHS


$ ./httpd -version
Server version: Oracle-HTTP-Server/2.2.15 (Unix)
Server built:   Apr  2 2011 23:51:27
Server label:   APACHE_11.1.1.5.0_LINUX.X64_110325.2001

Please note:

Ensure LD_LIBRARY_PATH variable is set and libaprutil-1.so.0 is present in that location.

Else you will get error as below when running httpd -version command.


./httpd: error while loading shared libraries: libaprutil-1.so.0: cannot open shared object file: No such file or directory

2) Check in Enterprise Manager

- Login to Enterprise Manager console /em.

- Select ohs component (eg: ohs1, ohs2 ....)

- Right click on it and select General Information

- You will see the version of OHS

- However this version info may not be reliable as it may show you can incorrect version in EM specially after upgrades if all upgrade steps are not correctly followed.

Even if you have run below commands after OHS upgrade, sometimes incorrect version may show up in EM.

 ./opmnctl unregisterinstance

 ./opmnctl redeploy

 ./opmnctl registerinstance

Related Posts:

FMW 12.1.3.0.0 - Applying Patch 19229422: OHS 12C UNABLE TO CONNECT TO WLS DYNAMIC CLUSTER

FMW 12.1.3.0.0 - Applying Patch 19948154: OHS SECURITY PATCH UPDATE 12.1.3.0.0 (CPUJAN2015)

Applying Patch 19948000: OHS SECURITY PATCH UPDATE 11.1.1.7.0 (CPUJAN2015)