How to restart single application in SAP DataIntelligence

[s__muscas]

Hello community,

we are working in a trial version of SAP Data Intelligence 3.0.3.

We noticed that often Connection Management, Metadata Explorer or some other application stop working, throwing a generic error like the following:

Error: could not acquire connection from pool: TimeoutError: ResourceRequest timed out.<br>    at connPool.acquire.then.then.then.catch (/project/src/libs/dh-hana-client/dist/lib/Middleware.js:137:18)<br>    at tryCatcher (/project/node_modules/bluebird/js/release/util.js:16:23)<br>    at Promise._settlePromiseFromHandler (/project/node_modules/bluebird/js/release/promise.js:512:31)<br>    at Promise._settlePromise (/project/node_modules/bluebird/js/release/promise.js:569:18)<br>    at Promise._settlePromise0 (/project/node_modules/bluebird/js/release/promise.js:614:10)<br>    at Promise._settlePromises (/project/node_modules/bluebird/js/release/promise.js:690:18)<br>    at _drainQueueStep (/project/node_modules/bluebird/js/release/async.js:138:12)<br>    at _drainQueue (/project/node_modules/bluebird/js/release/async.js:131:9)<br>    at Async._drainQueues (/project/node_modules/bluebird/js/release/async.js:147:5)<br>    at Immediate.Async.drainQueues [as _onImmediate] (/project/node_modules/bluebird/js/release/async.js:17:14)<br>    at runCallback (timers.js:705:18)<br>    at tryOnImmediate (timers.js:676:5)<br>    at processImmediate (timers.js:658:5)<br>    at process.topLevelDomainCallback (domain.js:126:23)

The only solution we found since now is to restart the server, but I would like to know if there is a way to restart a single application from System Management maybe?

I think this feature should be very usefull and will help SAP DataIntelligence to improve stability.

Thank you and best regards

Stefano

Edit: Cloud is AWS, thank you vitaliy.rudnytskiy, I think you have been luckier then me!

[Vitaliy-R]

Could you please add information about what cloud provider you are using to run Data Intelligence Trial? I haven't seen this issue yet after using DI Trial for more than a month.

[former_member690648]

I have to same error. I use GCP.

Minor thing, the DI_DATA_LAKE was set to S3 (AWS) and wasn't working. I tried to change it to GCP, but now Im stuck with the same error.