Quantcast
Channel: SCN : Discussion List - SAP HANA Cloud Platform Developer Center
Viewing all articles
Browse latest Browse all 3131

HANA XS - Debugger causes timeout error in HTTP requests

$
0
0

Hi together,

 

I'm currently developing a HANA XS Application on a productive HANA Cloud Platform. Since last week I am facing a very mysterious issue, which is very likely caused by the debugger (HANA Development Workbench (Web) and Eclipse).

 

The issue:

In the XS Application, I have different HTTP requests to 3rd-Party APIs. Everything is working fine so far. With the help of the debugger, we were already able to integrate two APIs to our application. Currently we're trying to implement a third API.

 

In order to continue with the implementation, of course, we need to debug the application, as we did it for the last two implementations as well.

But once we assign a session to the debugger, all HTTP requests (even those who have been working fine so far) throw a timeout error immediately after we drop the request. No matter if we set a breakpoint and pause the application or just let the application run.

When we kill the session and open the application again without the debugger assigned to the session, everything is working fine again for the two correct API implementations.

 

A week ago, we were able to debug that kind of requests without any issue and we didn't make any related changes on the backend, destinations or calling method. Restarting the HCP System didn't solve the problem.

 

var client = new $.net.http.Client();
......
oauth1.requestFor = function(dest, url, path, method, data, token, includeCB) {    var req = new $.net.http.Request("POST" === method ? $.net.http.POST : $.net.http.GET, path);    var request = {        url: url + path,        method: method,        data: data    };    var authHeader = this.toHeader(this.authorize(request, token), includeCB);    req.headers.set("Authorization", authHeader.Authorization);    var response = client.request(req, dest).getResponse();    var body = response.body ? response.body.asString() : "";    return body;
}

 

Please find attached the screenshot from the Chrome console, throwing the error, when the session is attached to the debugger.

 

Thank you very much for your assistance.

Best regards,

 

Ingo


Viewing all articles
Browse latest Browse all 3131

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>