After Appying SP2, RealTime XAI Outbound Messages To SSL Nodes Generate TrustAnchors Error
(Doc ID 2203607.1)
Last updated on SEPTEMBER 12, 2022
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.5.0.2.0 and laterInformation in this document applies to any platform.
Symptoms
XAI - XML Application Integration
SSL - Secure Sockets Layer
TSL - Transport Layer Security
URL - Uniform Resource Locator
HTTP - HyperText Transfer Protocol
HTTPS - HyperText Transfer Protocol Secure
MDM - Oracle Utilities Meter Data Management
CCB - Oracle Utilities Customer Care and Billing
OUAF/FW - Oracle Utilities Framework
Realtime XAI outbound message communications to SSL enabled nodes used to work prior to upgrading to Framework 4.3.0.2.0, but now they generate the following error and fail:
ERROR (domain.integration.RealtimeOutboundMessage) Problems invoking sender : java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty.
javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
The stack trace seems to indicate that functionality may have been updated at com.splwg.base.messaging.impl.RealtimeHTTPSender.executeMethod(RealtimeHTTPSender.java:183) as org.apache.http.components jar file versions, JDK, and keystore/trusstore may not have been changed when the issue started.
If you point to a non-SSL node, the communication flows unimpeded.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |