Getting HTTP Response Code 0 intermittently during Outbound REST to multiple different API providers

[MG Casey]

Since we updated to London Patch 8 Hot Fix 2, I am intermittently getting a "0" HTTP response code from my outbound REST calls within the instance.

The error returned is "java.lang.NullPointerException". The strangest part is that the normal response is still returned in Outbound HTTP Requests (it shows a normal 200 HTTP response code instead of 0). 

Anyone else have sporadic issues with RESTMessageV2 on this release? HI Support hasn't found much so far.

[MG Casey · Accepted solution]

ServiceNow support had to restart one of our nodes, which fixed this issue.

[Nazhath Mariam]

Hi,

While trying to make a REST call using below function:

var r = new sn_ws.RESTMessageV2(<OUR_API_ENDPOINT>, 'get');
r.execute()

throws: java.lang.NullPointerException

NOTE: Above parameters have been made generic for the question purpose but our code uses a proper endpoint which returns JSON responses while using POST UI client.

>> Build Version
-----------------------------------------------------------
Build name: Madrid
Build date: 07-10-2019_1243
Build tag: glide-madrid-12-18-2018__patch4a-07-09-2019

Any help will be higly appreciated.

Best Regards,
Nazhath Mariam

[MG Casey]

If it throws it every time, then it's typically an issue with the endpoint. But if it's inconsistent, I'd advise opening a ticket with ServiceNow Support.

[HV1]

We had the same issue, but the HI support recommended us to create a new property True/False "com.glide.communications.httpclient.verify_revoked_certificate" and set it to false.  That resolved the issue for us.