Vaadin 13 UI Components keeps reloading when deployed in Google App Engine - google-app-engine

I'm trying to deploy a Vaadin 13 app on Google App Engine. Of course I added the appengine plugin on pom.xml and appengine-web.xml on WEB-INF.
When I run this code:
mvn appengine:run
it works expected when viewed on localhost:8080.
However, when I deployed it on Google App Engine:
mvn appengine:deploy
Screens displays as expected, but most components doesn't work and keeps reloading (Please see chatbot tab on http://tricera-chatbot.appspot.com/chatPage)
I created this using HTML + base Vaadin 13 starter as skeleton.
I also tried to deploy the actual Beverage App starter from Vaadin site, and it behaves the same when deployed on App Engine (UI components unusable)

Posted this same question in Vaadin forum and someone answered:
Google App Engine does not support sticky sessions and will route HTTP requests to random servers which do not necessarily have an up-to-date version of the HTTP session for the user. Because of this, it won't work as the UI state is store in the HTTP session.
This sounds like GAE doesn't support Vaadin13. I'm still looking for workarounds (aside from switching platforms) and will keep you updated for future viewers.
source: Vaadin 13 Forum

Related

Google Cloud Platform - App Engine - can't stop and delete a version

I wonder is it possible to stop and remove an app's version? I use App Engine.
I tried many times but no success. Also I tried to do it if the app is inactive, still can't remove it.
As stated in the documentation you can stop an App Engine version only if your app has manual or basic scaling. Also, you cannot delete a version that is sharing traffic.
Meaning, if you only have one version in the default App Engine service, the only way you can delete the version of your App Engine app is by deleting your project.
There's currently a public Feature Request open to allow a full deletion of an App Engine app in a project which you can find here.
In any way, if you wish to, you can always disable the App Engine app completely as described here.

NodeJS Forge viewer error on Google App Engine

I've deployed my Forge viewer app based on the View BIM 360 & Fusion models tutorial, and I'm having trouble with authentication on Google App Engine.
Having set my callback URL to https://forgeviewer-218710.appspot.com/api/forge/oauth/token, the autentication does not work.
Is this because I need to set my ID, secret, & callback URL in the app.yaml file that App Engine uses to deploy? Or am I way off track?
I tried run your app, but got Error : 400 - Invalid redirect_uri, which means that the Callback URL on the Developer Portal is different from the one your specified on your app.
On the tutorial, at Create an app section, we use http://localhost:3000/api/forge/callback/oauth, but when creating the Forge app that you'll use on your live app, you should use the live version, in this case https://forgeviewer-218710.appspot.com/api/forge/callback/oauth (which is different from what you specified on your question, so please adjust).
To summarize, the callback url MUST match on Forge app registration and on your app live (assuming you have Nodejs, on the FORGE_CALLBACK_URL environment variable). Sorry I don't have experience deploying to Google App Engine.

Deploying PlayFramework Application to Google App Engine

For my new project I am planning to use PlayFramework and Google App-Engine. I was trying to create a sample application in playframework and tried to deploy it to app-engine.
it says the application is deployed successfully, but when I hit the url of my application
it shows a message "Your application is ready", But does not show the home page of my application.
I am using Play Framework 1.2 and GAE-1.4 plugin. I tried to deploy the application using the plugin and also using "appcfg".
The application works fine in local development mode but as soon as I deploy it to app-engine, the home page is replaced by "Your application is ready" message.
Can u guys tell me if I am doing anything wrong with the deployment of play-framework? I tried searching if anybody faced similar kind of issues in both google and SO but was not able to find any help.
Also, I read some post that GAE plugin does not work with Play-Framework 2.0(Note : I am using Play 1.2 in the above example) . I would like to know How can I deploy a play2.0 application in appengine.
Thanks a lot in advance!!!
Did you add application name and version number in appengine-web.xml before deploy?

Google App. Engine - Hosting our Web Application

All,
We are trying to host our web application on Google App. Engine with little success.
Here are the specifics:
The web application is built on HTML5, SVG & Javascript. We are using python 2.6 for upload. We initially used the following tutorial for upload but are getting errors once its uploaded.
Link to tutorial: http://www.labnol.org/internet/host-website-on-google-app-engine/18801/
We are getting errors in the appcfg.py python file. We are totally clueless how to go about using this so any guidance would be awesome, tutorials would be even more so.
UPDATE: Further to the outcry and Milimetric's helpful post, here is more detail:
We have managed to upload the web application onto the Google App Engine. Going into the dashboard, we can see the application is running (we can see the instance graphs and CPU stats), however, when we execute the custom link to the web application, we only get the 'Hello World' message.
We followed the tutorial by Milimetric & Rolled back the 'appcfg.py' to original state. Following the tutorial, we only made changes to the 'app.yaml' (inserted our application name). We didnt write any custom python script.
We are not getting any errors anywhere, only the message 'Hello World' upon executing the link in the browser window.
Hope the above is more useful.
Cheers,
If any of the following is redundant (or you already went through the steps), let me know and I'll edit. Just didn't know where to start or how familiar with app engine you were.
That tutorial will set up a functional app engine site. Were you able to get that running without any errors before adding your own code? Try running it locally with the launcher (localhost:8080 by default).
To add code, you have to start with the main.py file from the tutorial. Google app engine applications use the google.appengine.ext.webapp namespace to get started and listen to requests. In main.py, start with MainHandler and add code there.
To add more "routes" to your app, look at the WSGIApplication constructor: webapp.WSGIApplication ([('/(.*html)?', MainHandler)], debug=True) from their tutorial. So for example, you can have a route go to contact-us like this: webapp.WSGIApplication ([('/(.*html)?', MainHandler), ('/contact-us', ContactUsHandler)], debug=True).
As far as tutorials, the google app engine "Getting Started" tutorial is a good primer to get you in the mindset: http://code.google.com/appengine/docs/python/gettingstarted/
Google app engine is a cloud computing technology and it is designed for developing and hosting web applications it supports APIs, and frameworks. To solve this issue you ha eto understand app engine completely so to learn more about app engine visit the link above:
http://en.wikipedia.org/wiki/Google_App_Engine

Page not found on deploying Django-nonrel to Google App Engine

I'm a newbie to Google App Engine but have played around with Django in the past so I am trying to use Django-nonrel with GAE.
There's not much information online, but have followed these tutorials successfully:
http://blog.sidmitra.com/getting-up-and-running-with-django-nonrel
http://www.allbuttonspressed.com/projects/djangoappengine
I have managed to get setup fine and can get the 'It worked' page on local. However, when I upload my project to the Google App Engine Server I get a page with the following:
"Nonrel-testapp
The page you requested could not be found.
Powered by Django-nonrel"
I have used the following to upload:
python2.5 manage.py deploy
What am I doing wrong?
Are there any guides for uploading your Django app?
Thanks
You're not doing anything wrong. On the production server DEBUG is False, so you won't see that little "It worked" page. Since you're not the first one who was irritated by this I've just added a custom "It works!" page which also shows up on the production server. Just update your testapp source to see it.

Resources