WSDL Wizard empty and SOAP operator says "send message failed"

Document ID : KB000046550
Last Modified Date : 14/02/2018
Show Technical Document Details

 

Issue/Problem/Symptoms: 

Trying to use a SOAP operator and it fails with "Send Message Failed".  C20.logs return multiple error regarding SSL.

Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1884)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:276)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:270)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1341)
at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:153)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:868)
at sun.security.ssl.Handshaker.process_record(Handshaker.java:804)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1016)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312)

In this case the client had a Process Automation cluster.  Node 1 could use the same process and point to the same Service Desk WSDL without any issue at all. 

The WSDL Wizard in the process on node 2 would come up empty in the process when pointing to the Web Service URL on node 2.  SOAP UI on node 1 AND node 2 worked without any issue.

 

 

Environment:  

 

Process Automation 4.2 SP02 CP01

JDK 1.7.0_55

Windows

 

Cause: 


The cause of the issue was the existence of multiple domain.xml and Oasisconfig.properties files located in <Install Path>/server/c20/.config on node 2.  Every time there was a change to the Process Automation properties file or domain.xml they backed up the file by creating a new numbered backup file in the same (ie., domain_1.xml domain_2.xml, etc).  Java was reading these files as they contained the same extension. 

Resolution/Workaround:

 

1.  Moved all backup files out of the Process Automation working directories and to the system desktop

2.  Deleted the backup files from the Process Auto working directories

3.  Restarted the Process Automation services.

Once Process Auto came back up node 2 could connect to the WSDL and run the SOAP operator without issue.