XSA HXE 2 SPS3 - Gateway timeout

[SergioG_TX]

alright Gurus.... I need your help on this HXE

so.. I'm able to build my nodejs module... but i am unable to run it due to a Gateway timeout... I have 24GB RAM on my VM. I have re-deployed the development space.. i have re-started my service instances. (di-core, di-builder... my web app and nodejs modules...

I read and followed the instructions here: https://answers.sap.com/questions/452002/hana-express-20-sps2-web-ide-che-gateway-time-out.html

and looked into the blog from @Lucia, https://blogs.sap.com/2018/03/09/upgrading-web-ide-in-hana-express/ which may not apply since i am on HXE2 SP3...

why does the webide fails to run now? it seems like i have re-started and re-deployed the few places i needed to.

[SergioG_TX]

it seems so flaky .... i have restarted mi di-builder on the development space, as well as the web app and nodejs modules... still no luck... is this how hxe behaves for everyone?

[former_member258142 · Accepted solution]

I suggest you re-try this with HXE 2.0 SP03 Rev33 (released Oct 1, 2018). The WEB IDE version is:

4.3.32 (updated from 4.3.25 in HXE Rev31 in July 2018)

[Steven_UM · Accepted solution]

Hi Chris,

I recently installed SPS3 and I am facing the same issues (again) ...

See the initial mentioned other thread and my new comment ( https://answers.sap.com/answers/12629126/view.html )

[gjpeters · Accepted solution]

Hi Chris and Steven,

Same thing happens to me with the following....

SAP Web IDE for SAP HANA

Version: SAP Web IDE for HANA 2
SPS 03 Patch 60 ( Build 4.3.61 )

Any help would be greatly appreciated

[lsubatin · Accepted solution]

Hi Gary, Steven,

Please create a new question with details of the error, what the browser console is saying (F12) and the logs for apps webide, di-core and di-runner. Also please take a look at this: https://help.sap.com/viewer/5a2f3e85fa1a4eb891ab209d10d73a2e/SAPWEBIDE4HANA/en-US/c090e037d15a4e7eb3...

This original question does not have any relevant error details for us to help but we knew this was happening with that revision, which is not your case. There have been several releases between that date and now. I'm guessing your revision of HXE is 35?

Thanks,

Lucia.

[jmalla]

Hi Sergio - In terms of the NodeJS build, make sure to have enough memory and a faster drive. I have 40 GB on my Google Cloud Platform instance. Memory wise and for small apps this is fine. 24 GB is cutting in really close. But more so than that is the issue of the disk speed. NodeJS requires more I/O because of the NodeJS modules that it is pulling in the build process.

In my case, the system was working nicely when I had the disk on SSD. But I did a restore and without knowing chose the option without SSD and the performance deteriorated terribly. The SSD is 10 times faster.

So my suggestion is to have a better system - we have 40 GB RAM, 100 GB and we will be switching back to SSD and then it should be fine. You can definitely set the WebIDE, di-core, di-builder and di-runner all to have 1 GB and that will help but I think it's the disk I/O causing the issue.

We have been doing lots of HANA native development and now we have two implementations live on HANA XSA. Please feel free to connect with me if you would like more help. I am planning to do a free webinar on HANA native XSA development and lessons learned in the near future.

The new HANA XSA system is pretty cool but HANA Express has a long way to go (running this on less powerful systems).

I hope this helps.

Regards,

Jay

[lsubatin]

First, this question is from 2018 and the original issue was specific to a revision, a patch was released for that revision back in those days.

Second, the recommendation for XSA is to run on SSD. You'll see this in the guides both for HANA express and in general administration guides. I'd strongly recommend you read the admin guides if you are going to perform the administration and sizing yourself. You can learn about the tools to diagnose this kind of issue and perform the proper maintenance of the platform. You cannot expect a platform to "heal itself" just by restarting it and not performing any cleanup, diagnose or maintenance at all. You will also find the default image for HANA express is not ready for productive use out of the box.

Third, randomly scaling applications is not the solution to all problems and this is why basic knowledge of how the platform works is important. Actually, without diagnosing an issue like it's the case in this thread, it can make no difference or make it even worse.

[jmalla]

Hi Sergio,

Did you ever figure this out? I increased the memory is di-core, di-builder, and di-runner. The only thing that helped is restarting HANA. But there must be a better way.

Regards,

Jay

[SergioG_TX]

i dont think i was able to figure that out --- i am now trying to get the express sp4 working

[jmalla]

I ran into the issue after I had to restore from backup and the backup image was not set to SSD so I found out the hard way when things started taking really long and the build/run process really deteriorated. But after switching back to SSD and increasing the memory to 40 GB - it's running really well now. The SP3 onwards and the latest patch have definitely addressed many open items.