I am unable to deploy my application to google app engine however I can deploy it when I try 2nd or 3rd time. I get an alert on eclise as well as the log on console as below:
------------ Deploying frontend ------------
Preparing to deploy:
Created staging directory at: 'C:\DOCUME~1\bg92344\LOCALS~1\Temp\appcfg2387862893654282649.tmp'
Scanning for jsp files.
Compiling jsp files.
Scanning files on local disk.
java.io.FileNotFoundException: C:\DOCUME~1\bg92344\LOCALS~1\Temp\appcfg2387862893654282649.tmp\WEB-INF\lib\appengine-api-1.0-sdk-1.5.0.jar (Access is denied)
Debugging information may be found in C:\Documents and Settings\bg92344\Local Settings\Temp\appengine-deploy8040646126412995823.log
One thing that I found peculiar that when I go to Temp\appcfg2387862893654282649.tmp\WEB-INF\lib\ the jar appengine-api-1.0-sdk-1.5.0.jar dissapears after i get this alert, I guess it is not copying the jar completely. I dont know why :(
Can anybody help me out on this. Thanks in advance.
Regards,
BaleSabu
1 Login from Eclipse to your Google account (left bottom icon)
2 Check you application id before deploy. Should be same to your application.
3 Your user should have owner or admin role for application you want to deploy
Try cleaning and rebuilding your project before attempting to deploy again. Alternatively try to restart your IDE or computer. This fixed my errors in Android Studio.
Related
i have a react site that am trying to deploy to azure app service (free tiers windows) plan.
i am using VS-Code's Azure App service extention.
when i right click deploy to web app i get the error
11:44:47 AM amn-react-app: Starting deployment...
11:44:47 AM amn-react-app: Creating zip package...
11:53:39 AM amn-react-app: Zip package size: 298 MB
11:53:40 AM: Error: An error has occurred.
where to see the deployment logs to check what happened ?
update
following the update below i was able to see logs but they still not telling details.
I use vscode create a sample react project to test.
And I found, we can check delpoyment logs on portal.
Method 1
Method 2
I also try to use rest api to get deployments info, but failed because I don't find deployment id. If you are interested, you can also try.
Web Apps - Get Deployment
After finishing my project, I have right clicked on my project in order to deploy it on Google App Engine. In the available option when I clicked on "Deploy To Google App Engine" It is redirecting me to a browser asking some permissions. When I accept it, it ends up with a page with some token with a message that "Please copy this code, switch to your application and paste it there:"
At the same time in Netbeans console I am seeing the error
.Please enter code: Either the access code is invalid or the OAuth token is revoked.Details: invalid_grant
I did not get any popup to enter the authentication token I got from Google.
Where to enter this code ?
I am using Netbeans 7.3.
I had the same issue. I just deployed from the terminal using the update exec found in the App Engine SDK bin directory (Java App Engine).
So my command was:
$ ./appcfg.sh update ~/Development/path_to_app
This way you may enter the authcode into the terminal. Afterwards you should be able to deploy via NetBeans (make sure you have set email and password in NetBeans).
I Just had this issue couple of days ago.
Excuse me if I do not explain it right, just let me know it is my first post.
To solve it, you would need to run the cmd. Go to start and run cmd.
Navigate to C:\appengine-java-sdk-1.9.17\bin or whichever your appengine location is then type:
appcfg update "C:/path/to/app/directory/"
then it will run and show you the place to put the code.
For example:
C:\Ali\appengine-java-sdk-1.9.27\bin>appcfg update "C:\Users\almiskea\Documents\NetBeansProjects\WebApplication5\web"
Please enter code:
after you put it, this will show up:
Reading application configuration data...
Beginning interaction for module default...
0% Created staging directory at: C:\Users\almiskea\AppData\Local\Temp\appcfg7644042675237095331.tmp
5% Scanning for jsp files.
8% Compiling jsp files.
20% Scanning files on local disk.
25% Initiating update.
28% Cloning 13 application files.
40% Uploading 4 files.
52% Uploaded 1 files.
61% Uploaded 2 files.
68% Uploaded 3 files.
73% Uploaded 4 files.
77% Initializing precompilation...
80% Sending batch containing 4 file(s) totaling 5KB.
90% Deploying new version.
95% Closing update: new version is ready to start serving.
98% Uploading index definitions.
Update for module default completed successfully.
Success.
Cleaning up temporary files for module default...
Then your application is deployed.
I'm trying to get Vaadin7 app working on Google app-engine. I use app-engine sdk 1.8.5 with eclipse juno.
Deployment seems to work since I get:
------------ Deploying frontend ------------
Preparing to deploy:
Created staging directory at: '/tmp/appcfg4530509922106401908.tmp'
Scanning for jsp files.
Scanning files on local disk.
Initiating update.
Cloning 4 static files.
Cloning 8 application files.
Deploying:
Uploading 0 files.
Initializing precompilation...
Deploying new version.
Verifying availability:
Will check again in 1 seconds.
Will check again in 2 seconds.
Will check again in 4 seconds.
Will check again in 8 seconds.
Closing update: new version is ready to start serving.
Updating datastore:
Uploading index definitions.
Deployment completed successfully
However at the end of operation there is a pop-up saying:
An internal error occurred during: "Deploying <app-name> to Google".
java.lang.NullPointerException
Nothing is written to log file and I have no clue what kind of nullpointer is that. Accessing the application from web-browser gives HTTP 500.
Any tips on what can be the reason/possible solution?
Normally, after a successful deployment, the Google App Engine Eclipse plugin launches a browser tab pointing to your-app-id.appspot.com. If this fails, you can get a NullPointerException as you have described.
This is what happens to me, at least, with Eclipse 4.3 (Kepler) and app-engine sdk 1.8.6.
In this situation, your backend has indeed been deployed and it is safe to ignore this error. You will have to, however, launch or refresh your browswer tab manually.
I have checked and rechecked to see that I've done everything correctly, fixed a few problems with java 1.7 (set java compliance to 1.6) etc, and ran the program in develop mode and debug mode.
But when I go to the URL given (http://localhost:8888) I get a 404 screen:
HTTP ERROR: 404
Problem accessing /. Reason:
NOT_FOUND
Powered by Jetty://
The welcome file index.html is in the war directory and web.xml lists index.html as the welcome file. I get the same screen when I try to get the admin console at /_ah/admin as well. The logs I could find didn't show anything. Obviously GAE is working as it uses Jetty, any other port number I enter gives me a browser error:
Oops! Google Chrome could not connect to localhost:8887
Suggestions:
Try reloading: localhost:8887
Search on Google:
So what could be the problem? I checked file and directory permissions but I'm the only user on this computer ... any ideas or help is appreciated.
James
EDIT
I figured out the problem. My browser cache was holding a different package I had installed previously in my workspace. Simply clearing the cache after terminating all launches was the working solution. I was then able to continue with the excellent tutorial.
http://googcloudlabs.appspot.com/whatgae.html
GAE requires a controlled setup and a good place to follow and start is GAE tutorial. Here is a link GAE TUTORIAL
Look at my answer here.
You have to change Java version in Project Facet also.
GAE does not yet support being run with Java 1.7. Setting a compliance mode for Eclipse doesn't have any effect.
And that error you're getting form Eclipse for port :8887 is telling you that no application on your local machine is listening on that port. It provides no evidence one way or the other as to whether GAE is working.
Try again with Java 1.6.
I followed this excellent tutorial but, as it doensn't cover the deployment part, I tried to do it by myself.
So, I installed Springsource Tool Suite in Ubuntu.
Then, I create a "demo1" Roo project.
Next, with the built-in Roo Shell, I taped the following commands:
persistence setup --provider DATANUCLEUS --database HYPERSONIC_IN_MEMORY
entity --class ~.server.domain.Employee
field string --fieldName firstName --sizeMin 3 --sizeMax 20
field string --fieldName lastName --sizeMin 3 --sizeMax 20
gwt setup
After I checked "Use Google Webkit" in "Webkit Options", the project ran perfectly!
Then, to deploy the application to the App Engine, I taped the following command:
persistence setup –database GOOGLE_APP_ENGINE –provider DATANUCLEUS
which runs without any problem.
Then, i setup the AppEngine options (Application name and version ...) and clicked on the "Deploy App Engine Project" icon.
A popup shows and asks for the project name, email and password.
I gave all these information and clicked on "Deploy".
Unhopefully, an error occured and a popup showed with the following error message:
GWT compilation failed
And in the console, I got the following error:
Compiling module com.springsource.demo1.gwt.ApplicationCommon
[ERROR] Module has no entry points defined
I think that the problem is that GWT can't find the war file ...
Anyone succeded in deploying a GWT/Roo application by clicking on the "Deploy" icon?
Thank you very much,
Regards.
What you need to do is go to the Google -> Webtool Kit Settings... and remove ApplicationCommon from the Entry Point Modules list, and you probably need to remove some more, so only the configuration file with the Entry point remains.
Some background: The error is generated by the GWT compiler. When deploying GWT compiles the Java source to JavaScript. GWT uses module files with the extension: .gwt.xml which contain configuration information for the compiler. In at least one of these configuration files an entry point must be specified. By default the Webtool Kit Settings contain all those gwt.xml files from your project (there are probably 4), while only those with an entry point should be specified.
What version of STS were you using? I think this may be fixed with STS 2.3.3.M2...