I have made a UI5 application that uses an OData service pointing to SAP Gateway. This works correctly, however, I am noticing that if the app is left idle for a period of time (approx 10 mins), then the app suddenly starts getting the following error when trying to use this service:
"HTTP Status 503 - No application is available to handle this request"
Does anyone know why this could be happening and what I could do to fix this?
This is happening when running the app from the Web IDE.
As you have included "sap-web-ide" tag in your question, I assume this timeout happens during development when you run your app from web ide.
This is the timeout session from SAP Web IDE. Once time runs out, any call to the SAP Cloud Platform (including the one using a destination for your SAP Gateway system) will fail because your must reauthenticate (that can be done by refreshing the page).
If you deploy your app to SAP Cloud Platform or to your SAP Gateway system this short timeout won't happen.
Related
I am almost done with my first Test Sveltekit Application and want deploy the App in the next Days in my private Network. When I google for this I get flooded with "Deploy to Vercel, Netlify.... and so on" but I dont see much for deploying it the Application to an Server.
Can somebody explain what to do? The Application uses Endpoints.
You would likely want to run it through a Node server, for this you can use the adapter-node package, see the documentation for it for more information.
https://github.com/sveltejs/kit/tree/master/packages/adapter-node
The title pretty much sums it up. I understand the idea of bundling all of the packages together and deploying them to a remote server where a client (browser) will download it and execute it.
I have an issue with wrapping my head around the terminology of "deployment" in this scenario. Technically, every client will deploy the frontend application in its own environment every time, or am I missing something? It only needs to have the correct version available on the server to allow for that to happen.
From my understanding, you'd be deploying it by releasing it to the public (or a group of people). but the browser would just be reading and executing.
So I created a frontend application that just shows hello world.
I published or "deployed" my application to the server.
The client now executes my code and shows hello world.
We are using SF on premise and one on month we have some bug on Service Fabric Explorer that we cannot find by checking our app logs. In those cases app is not throwing exceptions and there is something happening when SF loads our app. Can somebody tell me where to search SF exceptions that are shown in cluster explorer (web site). I tried to look into c:\SfDevCluster\Log but I cant find where are those exceptions exists in logs.
I have deployed my Rest web services based SpringBoot java application in AWS EC2 server. Its deployed in Apache Tomcat server.
Client-side Angular4 application also deployed on the same server.
When I use a web browser from my desktop it works fine. I can see the logs are writing immediately in the server console.
But when I hit from a mobile browser I don't see any hit and logs in the server console for few minutes. But after a few seconds/minutes, I can see the logs writing on the server.
So what is wrong why it is getting delayed to reach my server from mobile browser?
I'm currently developing a (Java) backend for a mobile application using Google App Engine (SDK v1.8.8) and Cloud Endpoints. I'm using Eclipse (Kepler) with Google Plugin (v3.8.0) to develop/deploy the code.
I've been using Google API's explorer for many months during the development to test the endpoints and up until yesterday, everything was working well... if I ran App Engine locally, I could test the endpoints at:
http://localhost:8888/_ah/api/explorer
Likewise, I could execute against the remotely deployed version at:
https://1-dot-[my-app-id]-app.appspot.com/_ah/api/explorer
...in both cases, everything worked as expected.
However, as of yesterday, local execution no longer works... instead, my requests are sent to the remote (i.e. live!) version of my API. I'm still accessing API Explorer on localhost and according to it's output, my requests are still being posted locally... here is what is printed when I execute a function 'foo' on 'admin' endpoint:
Request
POST `http://localhost:8888/_ah/api/adminendpoint/v1/foo`
X-JavaScript-User-Agent: Google APIs Explorer
However, for some reason, these requests are being sent to the live/deployed instance of the API.
I restarted my browser (Chrome) and cleared it's cache, tried another browser (Safari), restarted the machine, re-deployed the API... It feels like something is being cached somewhere but I'm running out of ideas.
Does anyone have any suggestions?
The error has been fixed in the Google App Engine SDK for Java version 1.9.17, as indicated in the release notes (https://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes). I updated my libraries to 1.9.17, and the APIs explorer started working again for localhost.