Highlighted
Daniel Super Contributor.
Super Contributor.
1088 views

Unable to use API - javax.net.ssl.SSLHandshakeException: Remote host closed connection during handsh

Jump to solution

I have configured an Alert that triggers an Action.
That actions calls API (for operation orchestration) that runs an automation for an action.

I have imported the certificates from OO server and CA.

I'm getting the following error:

2018-10-02 18:20:52,795 [AlertThread for monitor SiteScope/1950477398/1950477399/1950477400/1950477403/1950477412/1950477415/2] (ApacheHttpUtils.java:488) ERROR - problem while sending data to URL: https://oo-stg.com/oo/rest/v2/executions/ error:  URL: https://oo-stg.com/oo/rest/v2/executions/, host: oo-stg.com, port: 80, UsingProxy: false, isHTTPS(SSL): true, javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake, currentRetry: 0

I have attached the configuration for the API

Capture.JPG

Any suggestion will be appreciated.

Thanks

0 Likes
1 Solution

Accepted Solutions
Daniel Super Contributor.
Super Contributor.

Re: Unable to use API - javax.net.ssl.SSLHandshakeException: Remote host closed connection during ha

Jump to solution

Let me clarify the problem first.

I'm monitoring a WebSphere using SiteScope.
When the monitor triggers an alert, the alert triggers an action.
The actions calls the Opertations Orchestration API to run a flow and that flow fix the WebSphere problem.

The problem was when Sitescope tried to call the OO API. I got this error.

2018-10-02 18:20:52,795 [AlertThread for monitor SiteScope/1950477398/1950477399/1950477400/1950477403/1950477412/1950477415/2] (ApacheHttpUtils.java:488) ERROR - problem while sending data to URL: https://oo-stg.com/oo/rest/v2/executions/ error:  URL: https://oo-stg.com/oo/rest/v2/executions/, host: oo-stg.com, port: 80, UsingProxy: false, isHTTPS(SSL): true, javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake, currentRetry: 0


I found out that the OO central server certficate was update on the server, but not on the F5. 

After the certificate was updated on the F5, we were able to use the API to connect from Sitescope to OO.

0 Likes
2 Replies
Regular Contributor.. Sttefany_P_SIS Regular Contributor..
Regular Contributor..

Re: Unable to use API - javax.net.ssl.SSLHandshakeException: Remote host closed connection during ha

Jump to solution

Hello Daniel, 

We hope you are doing good. 

Regarding your issue, could you please create a REST API monitor and check the behaviour?

Please let us know the results. 

If you have any doubt or question, please do not hesitate to contact us. It is a pleasure to help you. 

 

Regards,

Sttefany Padilla C.
SiteScope | Customer Support Engineer
MicroFocus.com  |  @microfocus 

0 Likes
Daniel Super Contributor.
Super Contributor.

Re: Unable to use API - javax.net.ssl.SSLHandshakeException: Remote host closed connection during ha

Jump to solution

Let me clarify the problem first.

I'm monitoring a WebSphere using SiteScope.
When the monitor triggers an alert, the alert triggers an action.
The actions calls the Opertations Orchestration API to run a flow and that flow fix the WebSphere problem.

The problem was when Sitescope tried to call the OO API. I got this error.

2018-10-02 18:20:52,795 [AlertThread for monitor SiteScope/1950477398/1950477399/1950477400/1950477403/1950477412/1950477415/2] (ApacheHttpUtils.java:488) ERROR - problem while sending data to URL: https://oo-stg.com/oo/rest/v2/executions/ error:  URL: https://oo-stg.com/oo/rest/v2/executions/, host: oo-stg.com, port: 80, UsingProxy: false, isHTTPS(SSL): true, javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake, currentRetry: 0


I found out that the OO central server certficate was update on the server, but not on the F5. 

After the certificate was updated on the F5, we were able to use the API to connect from Sitescope to OO.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.