Email Marketing Server (EMS) daemon failed to connect to Siebel Enterprise using HTTPS (SSL)

(Doc ID 1537738.1)

Last updated on SEPTEMBER 22, 2017

Applies to:

Siebel Email Marketing Server - Version 8.1.1.1 SIA [21211] and later
Information in this document applies to any platform.

Symptoms

Customer has enabled HTTPS for the Siebel Web Server and the URL for Web Services (EAI Object Manager) also uses HTTPS.

When attempting to EMS daemons to connect to Siebel Enterprise using HTTPS protocols the EMS daemons failed to establish connection to Siebel Enterprise. Tthe following error occurs.

ERROR
-----------------------
2012-11-20 17:09:52,179 [main] INFO OnPremiseAppListener Starting Primary service
Nov 20, 2012 5:09:53 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (org.apache.axis2.AxisFault) caught when processing request: com.ibm.jsse2.util.h: PKIX path building fail
ed: java.security.cert.CertPathBuilderException: unable to find valid certification path to requested target; nested exception
is:
com.ctc.wstx.exc.WstxIOException: com.ibm.jsse2.util.h: PKIX path building failed: java.security.cert.CertPathBuilderE
xception: unable to find valid certification path to requested target
Nov 20, 2012 5:09:53 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
Nov 20, 2012 5:09:53 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (org.apache.axis2.AxisFault) caught when processing request: problem accessing the parser. Parser already
accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser. Parser already accessed!
Nov 20, 2012 5:09:53 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
2012-11-20 17:09:53,527 [main] ERROR OnPremiseAppListener Unable to connect to siebel


The issue can be reproduced at will with the following steps:
1. Configure Siebel Enterprise to use HTTPS
2. Install and configure the EMS daemons to connect to Siebel using https for the parameter esd.handler.webservice.url in esd.properties.
3. Start the ESD daemon and it will not stay up.

Customer confirmed that if they change the Siebel Enterprise Web Server to use HTTP and configure the ESD daemon to http everything works fine.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms