I previously did not have any issues with this, as I have been deploying Azure web app from Eclipse with no issue. Usually it takes a few minutes, but currently it is taking forever with no real progress from what I can tell. I have tried restarting Eclipse as well as deleting the Azure app and recreating a new one. None of those work. Are there some settings I need to reset ?
EDIT: Yes it is a Web App created in Azure, and I previously had no trouble deploying at regular intervals. Last time however I wanted to abort the deployment and attempted to do so in Eclipse but it kept running and it seemed to be hanging so I shut down Eclipse and tried to deploy again but instead of taking just a few minutes, now it is stuck at the beginning with no progress.
I then decided to delete the web app, create a new one, and deploy to the new web app from Eclipse, but it is still the same with no progress.
EDIT: Adding Screenshots of the general environment and Azure configuration.
Just summarize for the above comments, the issue seems that Azure WebApp waits timeout to recover or reset for a failed deployment connection, so a suggestion is that trying to restart the Azure WebApp to recover or reset all status of the current instance fastly, or wait awhile then try to reconnect again.
But for some similar cases, if the above action failed, it's necessary for considering some metadata files in the current workspace, a valid way may be to create a new workspace to try to reconnect.
Related
After succesfully deployment via Github repo of my Spring boot Application in Azure's App Service i have still "Hey java developers!" page, i tried do this via Github and Github Actions, Github and Kudu, FTP, but result is allways the same. I'm out of ideas.
UPDATE
Today, I try again. I disconnect connection. And try to reconnect, I saw build area like below.
After Action completed, it works.
So I suggest you disconnect and reconnect to solve the problem.
PRIVIOUS
According to your description, I personally tested one side and your problem reappeared.
My troubleshooting steps:
First create a default page for webapp. (Under windows, it fails, indicating that this is not).
Deploy the webapp under linux and find that everything is normal.
From the Action on github, it was found that there should be a problem with the build in the deployment under windows.
In conclusion:
It is recommended to use linux to deploy webapp. As for the deployment failure under windows, it is recommended to raise a support ticket for help.
My test result.
Under Linux, after build action, we can see app.jar file under wwwroot folder.
I also move it to windows webapp, it doesn't work.
I am getting 503 Service Unavailable when call in Mule application... Call is not reaching to HTTP Listener I think and beside of HTTP Listener there is Set Variable... to Set Variable also not reaching call... Till day before yesterday it was working in all work spaces but suddenly it is not reaching to listener when I was trying after putting debug mode. But for other developer is not having any issue and he is able to receive call to Listener and other components. Current configurations everything is good. Can you please suggest what needs to check.
I had the same problem when I added an autodiscovery configuration for my application. Adding this to VM arguments folved my issue.
-Danypoint.platform.gatekeeper=disabled
I faced the same problem.
Everything was working, and suddenly (don't know why) I received the same 503 response.
I tried a lot to figure out what was going on.
Added new listeners and tested existing flows, which all went well.
Only my particular listener with the APIKit was never getting reached anymore.
I also disabled 'the gatekeeper' as suggested in the following article :
API-returns-503-Service-Unavailable-error-to-clients
Run -> Run configurations -> tab Arguments
I exported the project to a deployable archive file, with the checkbox 'only export project sources' selected. Tested this application on different PC's which went well.
Created a new workspace on my PC, imported the file , and the application failed again.
After a few other try & errors, I enabled the 'clear application data' -> 'prompt' selection box, and I disabled the 'APIKit settings' -> 'Show APIKit consol'.
I'm not sure if that consol had something to do with it, but after restarting the application and select YES on Clear application data , it worked well again.
Run configurations
I re-enabled the 'show APIKit consol' again, and it still worked fine.
This should solve your problem as well.
This is basically the same answer as the answer provided by user15476634, but with a visual description, and reasons why this error may occur.
For those who are wondering where to find Clear Application Data, please see below screenshot.
Most usual suspects in these type of issues is corrupted Application data due to following issues:
Trying to open multiple test consoles at a time
Working on huge payload and not enough memory allocated
Accidentally selecting the multiple run configurations and/or debug configurations at once
when you try to re-run the same app while an instance is already
running by disregarding the prompt/warning window (Do you want to stop the running application and start ...?)
For me, I had the same experience, the 503s appeared out of nowhere. Clearing application data did not work for me, setting
-Danypoint.platform.gatekeeper=disabled
did not work for me. I had to remove this xml tag from my global config
<api-gateway:autodiscovery ... />
It happened to me after turning on autodiscovery in order to deploy, so i had to remove these lines (autodiscovery) temporary then test then return these lines back in order to deploy
I am encountering a very weird problem in production. I have deployed a new application in production which is run in Tomcat server(version 7) using Windows services. This application is basically a batch processing which processes around 100-200 records at a time and generates their output in a flat file. When we run this application in production, the record's status changes from pending to verified(which is correct) and generates the flat file without any exception. However, when the batch process completes, all transactions are rolled back like nothing happened. Means, the record's status changes to pending, flat file is empty etc. This same application when running in staging or QA environment, it is running fine.
Can someone help me with this problem or at least guide me where should I start looking into it?
Since I don't know where the problem is, I am not attaching any sources or any error logs. Please let me know what details should I share?
Thank you
I use Eclipse to deploy my java code to Google App Engine. But over the past two weeks I found that it very often hangs at "Verifying availability" of the frontend. After waiting for a long time with a bunch of "Will check again in 60 seconds", the deploy fails. Through trial and error, I also found out if I delete the backend or sometimes delete the version completely and do a deploy again, it is more likely to succeed. Below is the error message:
Unable to update:
java.lang.RuntimeException: Version not ready.
at com.google.appengine.tools.admin.AppVersionUpload.commit(AppVersionUpload.java:572)
at com.google.appengine.tools.admin.AppVersionUpload.doUpload(AppVersionUpload.java:143)
at com.google.appengine.tools.admin.AppAdminImpl.doUpdate(AppAdminImpl.java:328)
at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:52)
at com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngineBridgeImpl.java:433)
at com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(DeployProjectJob.java:148)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Thanks in advance.
I use GAE Python. When I have problems with deploying an application I have to rollback first in order to deploy the application again. Sometimes deploying fails (in the way you describe) during maintance hours by the app engine team. To solve this, I had to wait a couple of hours.
I am getting a really annoying problem. In my application, whenever i need to change client code, the refresh make the new fix works
However, when editing server code, i need to stop the current application and run again. When the application is big, this takes a little time.
Is there a way to force update the current running server code???
i need to stop the current application and run again
[...]
Is there a way to force update the current running server code???
Absolutely! It's not necessary to stop the server when you need to refresh the server side code: In the "Development Mode" view (in Eclipse), click the icon with the two yellow arrows. This application reload is much quicker than a server restart.
If you are using Eclipse run your back-end application in debug mode instead of run mode and that usually gets you a little closer due to its incremental compiler.
Check this out on how to use an external server with GWT http://code.google.com/webtoolkit/doc/latest/DevGuideCompilingAndDebugging.html#How_do_I_use_my_own_server_in_development_mode_instead_of_GWT's
Run your server side code in some other server like tomcat. And start the gwt application in noserver mode. But if you change any rpc related classes in client side you have redeploy the code in tomcat server.