"Unexpected error occurred communicating with MOCA server: General SSLEngine problem."
Problem
I receive the error: "Unexpected error occurred communicating with MOCA server: General SSLEngine problem." while trying to connect to a JDA WMS instance in Cycle.
Solution
This error occurs when there is an issue with SSL validation. Cycle provides Advanced Settings that work with the machine's default SSL validation, skips validation or self signed certificates.
Read the Advanced Settings section of the User Manual and configure Cycle to fit your organizational needs.
Related Articles
"Unexpected 302 status code received from MOCA server."
Problem I receive the error: "Unexpected 302 status code received from MOCA server." while trying to connect to a JDA WMS cloud instance in Cycle. Solution This error occurs when the cloud URL is used without /service on the end of the connection ...
Can Cycle execute MOCA and Local Syntax?
Problem Cycle Features built to interact with and test the JDA WMS need to run queries, execute statements and perform validations directly against the database. Solution JDA WMS provides a framework to ease database interaction called MOCA. Cycle ...
MOCA Server or Web API Step Timeout Error on Long Running Command
You may see the error message below in your tests if you have a MOCA command or a Web API step that takes longer than 60 seconds to complete. This error message is due to Cycle expecting a response from the MOCA server or the Web API endpoint within ...
TLS and SSL Errors With Connection Steps in versions Cycle 2.10+
The Java version shipped with Cycle was updated with the Cycle 2.10 release. As a result, you may receive error message similar to the example messages below when running steps to establish DB connections in Cycle 2.10+: javax.net.ssl.SSLException ...
How to control Blue Yonder WMS authorization of Cycle MOCA connections
Problem When connecting Cycle to a Blue Yonder WMS, it may be necessary to limit Cycle's access. Solution The Cycle MOCA connection step, I connect to MOCA at "<ADDRESS>" logged in as "<USERNAME>" with password "<PASSWORD>" includes a check of the ...