This application does not exist (app_id=u'google.com:nbsocialmetrics') - java

I know others have posted similar issues but after trying their solutions I think this is a different problem.
I'm trying to get a multi-module application functioning for Google App Engine. I'm developing it from this sample code.
I was able to get my application running successfully in the development server but I encountered the following error when I tried to upload to Google App Engine with the command mvn appengine:update:
Error Details:
Nov 05, 2014 10:23:51 AM org.apache.jasper.JspC processFile
INFO: Built File: /guestbook.jsp
com.google.appengine.tools.admin.HttpIoException: Error posting to URL: https://appengine.google.com/api/appversion/create?module=nbsocialmetrics-frontend&app_id=google.com%3Anbsocialmetrics&version=1&
404 Not Found
This application does not exist (app_id=u'google.com:nbsocialmetrics').
Unable to update app: Error posting to URL: https://appengine.google.com/api/appversion/create?module=nbsocialmetrics-frontend&app_id=google.com%3Anbsocialmetrics&version=1&
404 Not Found
This application does not exist (app_id=u'google.com:nbsocialmetrics').
Please see the logs [/var/folders/dp/v_lw6kqx16bf7743hs5t9phc0000gn/T/appcfg8240676105577823958.log] for further information.
I've listed a bunch of references to similar problems but here is a summary of what they say and why it didn't work for me:
1] Permissions - Make sure you have permission to upload code to this google account. I verified by going to http://appengine.google.com, clicking my app, nbsocialmetrics, and clicking permissions. There it lists the correct Google account and it says the Role is owner.
2] Delete cookies - To ensure my credentials hadn't been cached, I deleted the file ~/.appcfg_oauth2_tokens_java (I'm on a Mac). Apparently this file used be called .appcfg_cookies which you'll see in the references I've listed below.
3] appcfg.sh --no_cookies - Some people suggested another approach beside #2 above: call c. However, I'm using mvn appengine:update and it would take a lot of work to figure out how mvn appengine:update and mvn appengine:update relate to each other. So I didn't try this.
References to similar problems whose suggestions did not work:
GAE/J This application does not exist (app_id=u'application-id')
Getting Error 404, application not found error when deploying to Google App Engine
This application does not exist (app_id=xxx)
This application does not exist - GAE
http://juplo.de/log-out-from-wrong-account-with-maven-appengine-plugin/
http://forums.udacity.com/questions/6014266/solved-unable-to-deploy-my-app-this-application-does-not-exist
https://code.google.com/p/googleappengine/issues/detail?id=5331
http://techspalace.blogspot.com/2011/08/solved-this-application-does-not-exist.html

If you are using windows,
you can try after delete this file
C:/Users/{username}/.appcfg_oauth2_tokens_java
(maybe somthing like this file.)
I'm using eclipse maven plugins to build and packaging.
By this way i could fix it !
References : https://cloud.google.com/appengine/docs/java/tools/uploadinganapp

I noticed how the error I got was different from other reports of this issue. Notice the prefix google.com: in the error message I received:
This application does not exist (app_id=u'google.com:nbsocialmetrics').
This prefix wasn't in the other reports of this problem. So I tracked that prefix down to the file I was modeling after: appengine-application.xml.
My solution was to remove the prefix from my appengine-application.xml so it now reads this:
<application>nbsocialmetrics</application>
Instead of:
<application>google.com:nbsocialmetrics</application>
I have no idea why that prefix was in the sample code.

Related

Can't run dotCMS - cms500Page

I downloaded the zip file of dotCMS two days ago from http://dotcms.com/download/. I followed exactly step by step the instructions of dotCMS documentation and I managed to connect correctly the dotCMS with mySQL (http://dotcms.com/docs/latest/DatabaseConfiguration).
The problem is that when I am running the Apache tomcat (by executing the startup.bat file), a blank page appears on localhost:8080/ and sometimes a page appears containing the number 500(of course in the ROOT folder in webapps I have the dotCMS files). Also in catalina.log I see the following error:
ERROR org.apache.jsp.portal._500_jsp - cms500Page
Any idea about how to fix this?
Most likely your database is not connecting or is misconfigured. Make sure that you point dotCMS to an existing, though empty, db. Also insure that your username/passwords work using the exact same ip/hostname as your connection string.
You will find more information about your db error in the log files, either the tomcat/logs/catalina.out or the tomcat/webapps/ROOT/dotsecure/log/dotcms.log
See this page for more information on how to install dotCMS
http://dotcms.com/docs/latest/installation
I had the same issue few weeks back and managed to resolve it.
The issue might be because you didn't use terminal command to extract the package as mentioned here.
Try using :
tar -zxvf dotcms_X.X.tar.gz

This application does not exist - GAE

This application is live. I previously used this project for php, now I am experimenting with Java and I cannot get the project to upload. Below is the error message I get:
com.google.appengine.tools.admin.HttpIoException: Error posting to
URL:
https://appengine.google.com/api/appversion/create?app_id=laraveltest2014&version=1&
404 Not Found This application does not exist
(app_id=u'laraveltest2014').
I tried adding the parameter below and it had no effect.
--no_cookies
If you logged in with different google account previously, try deleting these two files from home directory:
.appcfg_oauth2_tokens_java
.appcfg_cookies

Running Play framework 2.1.1 and getting "exception when typing play.Project.javaCore"

I'm trying out the sample apps that come bundled with the play download and they appear not to be working, but the exception I'm getting isn't clear about what's going on.
I've previously been able to create new applications in Play ok, so this seems a bit odd.
I switched to the samples folder and simply trying running "play":
$ cd ~/play-2.1.1/samples/java/helloworld/
$ play
Which should bring up the play console.
Instead I get this output + exception:
[info] Loading project definition from /home/john/play-2.1.1/samples/java/helloworld/project
exception when typing play.Project.javaCore
class file needed by PlayReloader is missing.
reference type SBTLink of package play.core refers to nonexisting symbol. in file /home/john/play-2.1.1/samples/java/helloworld/project/Build.scala
scala.tools.nsc.symtab.Types$TypeError: class file needed by PlayReloader is missing.
reference type SBTLink of package play.core refers to nonexisting symbol.
at scala.tools.nsc.symtab.classfile.UnPickler$CompileScan.toTypeError(UnPickler.scala:66)
at scala.tools.nsc.symtab.classfile.UnPickler$CompileScan$LazyTypeRef.complete(UnPickler.scala:79)
at scala.tools.nsc.symtab.classfile.UnPickler$CompileScan$LazyTypeRef.load(UnPickler.scala:81)
at scala.tools.nsc.symtab.Symbols$Symbol.typeParams(Symbols.scala:913)
... <rest omitted for brevity> ...
[error] (compile:compile) java.lang.Error
Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore?
It looks like it's not resolving a dependency or something as it's complaining that it's can't find a specific class (SBTLink?)? But really not so sure what's going on here.
Anyone got any ideas on what I'm doing wrong?
UPDATE: actually this appears to be happening for other play projects - so it's not specific to the sample apps.
I've just been able to make a new app ok (using "play new"), but when I switch into it's folder and run "play" I get the same exception as above.
Ok so in the end I had to delete the repository cache - I'm guessing it'd got corrupted somehow. Which would explain why it was complaining about not being able to find some class files.
Another possibility about why it stopped working may be due updates to java itself. There had been at least one update to java (to 1.7.0_25 on ubuntu) since I last tried running play, so there may have been some issue there (perhaps minor binary class file change?).
My play folder is in my home directory, so I did the following:
$ cd ~/play-2.1.1/
$ rm -r repository/cache/
Then tried running play again inside one of the sample app folders. It took a while (presumably as it was rebuilding the cache) and then worked.

Publish failed using Ant publisher (Eclipse/datanucleus)

I am being driven mad the following (apparently hard) error from eclipse.
Publish failed using Ant publisher
Resource is out of sync with the file system: '/MyServlet/build/classes/com/inver/hotzones/database/BaseNetworkData.class'.
I have seen comments on similar errors where refreshing eclipses view of the project helps but it is not helping me. Have tried cleaning the project, removing it from the webserver, deleting war files but cant seem to clear it. I have reset my TMPDIR variable so that it uses a directory on the same filesystem as that appeared to be another possible cause.
The error occurs on classes which have been enhanced by datanuculeus. I have auto-enhance on the project. The other references to this problem indicate that it is due to Eclipses view of the project being out of step with the filesystem, and I am guessing that this has something to do with thedata nucleus enhancement.
Any ideas?
Thanks.
I am using Eclipse 3.5.2 with latest datanucleus pluggins.
Stack trace
org.eclipse.core.runtime.CoreException: Resource is out of sync with the file system: '/MyServlet/build/classes/com/inver/hotzones/database/BaseNetworkData.class'.
at org.eclipse.jst.server.generic.core.internal.publishers.AbstractModuleAssembler.copyModule(AbstractModuleAssembler.java:172)
at org.eclipse.jst.server.generic.core.internal.publishers.WarModuleAssembler.assemble(WarModuleAssembler.java:31)
at org.eclipse.jst.server.generic.core.internal.publishers.AntPublisher.assembleModule(AntPublisher.java:167)
at org.eclipse.jst.server.generic.core.internal.publishers.AntPublisher.publish(AntPublisher.java:128)
at org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour.publishModule(GenericServerBehaviour.java:82)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:949)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1039)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:872)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2731)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:278)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Error : "javax.servlet.ServletException: Failed to load test suite [SampleTest], Reason is [Class not found "SampleTest"] "

Hi i am new to cactus and when i am using tomcat5.1 and have included all the necessary jars. But when i am trying to execute it, it is showing the error,
Error : "javax.servlet.ServletException: Failed to load test suite [SampleTest], Reason is [Class not found "SampleTest"] "
Please let me know what the problem is??
If you are trying to run the Quick Start tutorial from the Cactus web site, I believe it no longer works.
Here's a mention in the release notes of 1.8.1.
Release Notes - Cactus - Version 1.8.1
Bug
* [CACTUS-124] - Cannot run the Servlet Example
I get the same error message with version 1.7.x.
I just started researching this product, so I'll post an answer if I find one. Hopefully someone else will have an answer with the extra info I have provided.
EDIT:
Found a work around. Looks like it's an issue with package names. I re-compiled the two files using the default/no package and it worked.
EDIT 2:
I looked up CACTUS-124 in the bug database and it's not related. Also I believe only the class files that extend ServletTestCase need to be changed to the default/no package name.
You need to include the package ie:
http://localhost:8080/myapp/ServletTestRunner?suite=common.TestEverything
Would run the suite TestEverything in the common package.

Categories