Thanks in advance. When I try to run a simple application with two jsps, 2 java classes and one servlet I get the next message:
"build-impl.xml:1051: The module has not been deployed.
See the server log for details."
I am using Oracle WebLogic Server, and I've lately been having a problem...when I try to stop it by right-clicking on its name(Services tab and then Servers tab on NetBeans) and clicking on the stop button, I get a warning telling me the Oracle WebLogic Server couldn't be stopped.
I'm not sure if both problems are related.
I spent days looking for a solution, but didn't find one.
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.
form this morning (January 12 2016) there is a warning message appearing when we deploy to Google App Engine. We don't use PageSpeed so it's surprising that it tries to post something to its URL.
95% Closing update: new version is ready to start serving.
98% Uploading index definitions.
I 12, 2016 10:45:06 DOP. com.google.appengine.tools.admin.AbstractServerConnection send1
WARNING: Error posting to URL: https://appengine.google.com/api/appversion/updatepagespeed?module=yyy&app_id=xxx&version=1&
404 Not Found
You are using a decommissioned API. Please upgrade to a more recent version of the App Engine SDK which can be found at:https://developers.google.com/appengine/downloads
This is try #0
We use latest GAE SDK (1.9.30), latest gradle appengine plugin (1.9.30) and gradle task that we run is appengineUpdate.
Why is that Pagespeed warning appearing now and wasn't appearing before? How can we get rid of it?
Thanks,
Michal
I filed a new bug report here:
https://code.google.com/p/googleappengine/issues/detail?id=12665
Please star it if you are affected. This should help fix the problem upstream, at Google.
UPDATE 2016-01-20, FIXED
Quote from Google, see link above:
"This issue is now fixed. Here is a summary of the cause:
The PageSpeed service was switched off on 3rd August. However, the App Engine deployment API continued to have a call for it. A couple of days ago, a new App Engine minor version was released to production, in which this call returns a HTTP 404 and the warning message above. Unfortunately, this App Engine change was released to production before the corresponding change in the App Engine SDK, which is still calling the decommissioned API endpoint. The error message you have received was harmless, the SDK still completed the app deployment.
The SDK team is working on preventative action items that will avoid asynchronous releases."
Pagespeed has been decommissioned, that's why you're having these problems(although a bit late then expected as it was decommissioned 1.12.15).
For more info:
https://cloud.google.com/appengine/docs/deprecations/pagespeed
Also it's worth checking once in a while:
https://cloud.google.com/appengine/docs/deprecations
Here is a reply from Google on this issue
As people have pointed out above, this is indeed a bug in the SDK — more specifically, an inconsistency between the SDK and the App Engine deployment API. However, it's harmless: the SDK handles the error gracefully, your app deployments will not be affected, and it's safe to ignore the message. If you're using the current SDK (1.9.30 at the time I send this message) then you can safely continue to do so.
The reason for the error is that the "updatepagespeed" call is to be removed from both the API backend and the SDK frontend. Due to an oversight and different release schedules, the API change went out before the SDK change, so the SDK is still invoking the obsolete RPC. Sorry about the noise! Our engineers are fixing the inconsistency, and we'll make a notification here when the fix has been posted.
Dave Hughes, Google Cloud Platform Support
We had the same problem, and it was partly caused by a pagespeed entry in appengine-web.xml file.
The second warning is caused by a bug in the Google SDK, but it is harmless, the deploy succeeds. (According to the google comments in the link by CaptainCrunch: https://code.google.com/p/googleappengine/issues/detail?id=12665)
As toadstool said. Just remove a entry in appengine-web.xml related to pagespeed and done. Thanks everybody for the responses.
I just commented the pagespeed tag I had in my appengine-web.xml
<!--
<pagespeed>
<url-blacklist>http://*/sistema/*</url-blacklist>
<enabled-rewriter>MinifyCss</enabled-rewriter>
...
...
</pagespeed>
-->
On Ubuntu 12 server and Tomcat 7, I load test my spring mvc application for one specific REST get method. (using an online load test tool)
For 1 user per second and over a minute it works fine. But when I load test 50 users per second, after a short while tomcat shutsdown, so I have to restart it again. I checked logs but no error was there.
Where can I start to find the problem? Becoming slow, or unresponsive could be something that I could understand, but shuting down dont make sense.
I don't know why my Heroku application is in crashed state.
Log and code at https://github.com/jstar88/LibreTitan/blob/master/log.txt
Running application at http://libretitan.herokuapp.com/
The problem is that your database is in an inconsistant state, so Play wants to run DOWNS evolutions, but you have not started your server with -DapplyEvolutions.default=true and -DapplyDownEvolutions.default=true. If this is a production system, I would not recommend doing that until reading about and fully understanding how Play's evolutions work because DOWNS could cause destructive changes to your data. The documentation can be found here:
http://www.playframework.com/documentation/2.1.0/Evolutions
Since you are running on Heroku, be sure to also set evolutions.use.locks=true so the evolutions will still work if you scale to more than one dyno.