Hybrid Testing - HANA IP Allowance

[h-hild]

Hi together,

When you do hybrid development with CAP, you need a direct connection from your local machine to HANA instance.
In this case, the source IP should be allowed from HANA side and this is not allowed by default.
Default is "Allow only IP addresses from Cloud Foundry in this BTP region" which blocks the connection.

Therefore maybe we should mention this as a hint in the Hybrid Testing documentation.
Here the Link to the current documentation: https://cap.cloud.sap/docs/advanced/hybrid-testing

Thanks,
Heinrich

[renejeglinsky]

Hi @h-hild ,

Thanks for opening this issue.

We have that information in our troubleshooting guide. And we've included a link:

Have you not seen this link 👆 or was the content not helpful?

All the best,
René

[h-hild]

Hi @renejeglinsky ,

oh, i fear i have missed this link, but i have looked for troubleshooting. The error i get was not "(RTE:[89008] Socket closed by peer".

I had this error on hybrid testing:

The root cause is the same, but this troubleshooting guide has the reference to deployment errors. For me the deployment was working. So i had not looked on this place :(.

Perhaps it would be sufficient to include in the troubleshooting guide that this error is not only relevant during deployment, but also during hybrid testing.

best regards,
Heinrich

[renejeglinsky]

That is interesting! I need to test that as well.
I'll keep you updated on our actions. If I can reproduce it, I'd tend to add a separate troubleshooting entry, so that it fits better to this scenario and error message.

[renejeglinsky]

For this error we do have a troubleshooting entry under the Node.js section:
https://cap.cloud.sap/docs/get-started/troubleshooting#why-are-requests-occasionally-rejected-with-acquiring-client-from-pool-timed-out-or-resourcerequest-timed-out

Would be a different root cause but is it possible that this also applies to your situation?

[h-hild]

I had seen this entry when I was looking for a solution. This is exactly the error I had. Maybe it makes sense to simply add a second root cause to the list here, which again points to the problem with the IP restriction in the HANA Cloud?