Hi,
No it means that the name will no longer be usable, unfortunately.
Application names appear to last forever, no matter whether the app has
been deleted, so the only way to retain the same app name externally is to
use the HRD migration tool.
Cheers,
Simon
On Monday, 19 March 2012
,
Simon
On Monday, 19 March 2012 18:52:12 UTC, Pavel Lisa wrote:
No, that can’t work, the HRD migration tool doesn’t offer to migrate to
the same application id.
Dne pondělí, 19. března 2012 18:19:19 UTC+1 Simon Knott napsal(a):
Hi,
No it means that the name will no longer be usable
Hi,
Have you tried filling out the quota
formhttp://support.google.com/code/bin/request.py?contact_type=AppEngineCPURequest,
referenced from the Quotas
documentationhttp://code.google.com/appengine/docs/quotas.html#Channel
?
Cheers,
Simon
--
You received this message because you are
Hi,
Even if MemCache doesn't go down, there is no guarantee that MemCache data
will be there from one (milli)second to the next - it's a cache and its
data should be treated as entirely transitory.
To answer your original question, if MemCache went down then when it came
back it would be
Hi,
The calculation for datastore writes for new entities is:
2 Writes + 2 Writes per indexed property value + 1 Write per composite
index value (see
http://code.google.com/appengine/docs/billing.html#Billable_Resource_Unit_Cost
for
more information).
If you have 14 simple properties, then
Are you using any other third-party libraries for logging?
I've just had a look at my project and I haven't done anything special
apart from put a logging.properties file at the root of the classpath, and
logging output is fine with tests (attached it just for info). Even if I
delete that
It looks like you've compiled the Hello World application with JDK 7 - GAE
only supports JDK 6 applications currently.
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Have you tried setting log4j.logger.org.springframework.web=OFF? The log
comments aren't coming from the security package.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
When I get near a computer I'll see what settings I've got. I swear I see log
output for my unit tests.
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Hi,
I'm afraid there is no way to connect to external databases.
Currently the only access you can have is either to the GAE big table-based
datastore via various APIs (JPA, JDO, low level API, or third party such as
Objectify/Twig/Slim3), or to external applications via an HTTP interface.
Which SDK are you developing against - are you actually developing against
1.6+? Do you get any error in your server logs?
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Suresh,
Based on your previous comments about web services and also this one,
you're either incredibly lazy or are simply a very junior developer and
completely lost. The very first demo application on that link has an
example of using JDO with GAE, and many of the other apps have some
Whilst you don't control the maximum version that GAE supports, it does honour
whichever version you've specified in your app configuration file.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web
Hi Suresh,
It might be worth having a look through some of Brandon's examples at
http://code.google.com/p/gwt-examples/
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Suresh, a 404 error means that the URL you have pointed your SOAP client at
doesn't exist.
What URL are you attempting to connect to?
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Hi,
I highly recommend that you read all of the documentation at:
- http://code.google.com/appengine/docs/java/datastore/overview.html
-
http://code.google.com/p/twig-persist/wiki/Comparison#Objectify_and_SimpleDS
-
Hi,
Your best bet is the datastore, as this is probably the most reliable
shared service. You could potentially share state in a backend server, but
these too have a tendency to go down.
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App
Hi,
This morning I'm hitting OutOfMemory exceptions on some really trivial
code, and it's all coming from either AppStats or logging:
Uncaught exception from servlet
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2935)
at
Well I've just tried an F2 and F3 with exactly the same results - one call
to a particular handler just blows the memory completely. Seems to be a
general failure around AppStats and Memcache usage today!
com.google.apphosting.api.ApiProxy$CancelledException: The API call
memcache.Set() was
Move the processing into the task queue - individual tasks can process for 10
minutes.
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Suresh,
I don't mind answering queries when there is a genuine problem, but I'm not
going to type gae java task queue into Google for you. You've got to do
some of the leg work yourself.
As for your other query, if you want to do publish-subscribe in the client
then look at Pubnub.
Yes, that's completely possible.
What persistence framework are you using, or are you using the low level
API? They all have different ways of turning off individual property
indexes. It should also be noted that once you change configuration, you
actually have to load and re-persist all of
Ah it would have helped if I'd read your original post - I believe (and I
haven't bothered with DataNucleus for a long time) that you need to add
that annotation for every property you wish to be unindexed.
Cheers,
Simon
--
You received this message because you are subscribed to the Google
What do you need to use JMS for - connecting to a third-party application,
outside of GAE?
If not, have you looked at the Task Queue API?
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on
Hi,
A lot of the answers to your questions can be found by using a search
engine, Suresh, and doing some work for yourself. JMS does not support
HTTP by default - you'll have to find a JMS provider which has an HTTP
connector.
As for the 500 error, you need to look in your appengine console
Hi,
Do you normally do development Suresh, or are you just getting into it? If
it's the latter, I'd suggest not using GAE as your first attempt, as it
really isn't the easiest development or test environment to start on.
The error you're getting is because the target of your SOAP call doesn't
Hi,
Unless your JMS Queue provider supports HTTP connectivity, you will be
unable to use JMS on GAE.
HTTP is currently the only communication protocol supported on GAE-hosted
applications.
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App
Hi,
The GAE sandbox environment is restricted from reading arbitrary files from
the file system, just as the production environment is. You need to deploy
the XML as part of your web application and then load the file.
See http://code.google.com/appengine/kb/java.html#readfile for more
Hi,
We actually get 28hrs for free - it allows for a couple of extra instances
being spun up by the scheduler on the odd load spike, without having to
face charges.
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
Hi,
The limit is actually 5000 indexed properties per entity - see this post
for a more detailed explanation:
https://groups.google.com/d/msg/google-appengine/1fTct9AO1MY/FmjJBcye9OAJ
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App
Another couple of useful links:
http://stackoverflow.com/questions/5131247/google-app-engine-datastore-index-cap
and
http://code.google.com/appengine/docs/python/datastore/queries.html#Big_Entities_and_Exploding_Indexes
--
You received this message because you are subscribed to the Google
That error looks like you are using the wrong version of the supplied
DataNucleus library with GAE SDK 1.6
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
A couple of other people in the group have resolved this issue by JARing up
their custom classes, rather than loading them up from the WEB-INF/classes.
You'll notice that all of your errors come from class resolution or
classpath scanning - it seems the file system on GAE is particularly slow,
JRE7 isn't supported, you need to use JDK6.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/ro2mMcBE-3UJ.
To post to this group, send
Thanks for the update Jerome. I had wondered whether the error had
occurred in Session management, since you weren't calling it explicitly.
This definitely needs to fail invisibly - a failure in Memcache, when the
datastore is still available, shouldn't cause session management to fail!
Can you post one of the exceptions which was thrown from your JSP pages?
That seems a little strange to me!
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
As far as I can see, from SDK 1.5.5 onwards the following is true:
Each incoming HTTP request can be no larger than 32MB.
This came from http://code.google.com/appengine/docs/quotas.html
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java
Hi,
Unfortunately setting the namespace in the init method won't work, as the
setting of the Namespace is on a per-thread basis (see
http://thoughts.inphina.com/2010/09/16/multi-tenancy-in-google-app-engine-scope-of-namespacemanager/
for more info on how it works under the hood).
The better
And I've just re-read your post - apologies, as this was exactly what you
were suggesting and it will work fine!
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Re-reading your post, I've realised that this is almost what you were
proposing anyway - the only difference is that you can't use the init
method.
You'll need to store the namespace passed into the init method and use it to
call the NamespaceManager in the doFilter method.
--
You received
Wow, great job!
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/_i2OYZoqR_UJ.
To post to this group, send email to
3-4 seconds
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/eGjoKqAMLQkJ.
To post to this group, send email to
It's much better practice to set the ThreadLocal as final and static, in my
experience. i.e.
private static final ThreadLocalUserData localUser = new
ThreadLocalUserData();
If you don't do this, then you've got the danger that a separate thread can
re-initialise the ThreadLocal between
There is a very high possibility that your application will run in multiple
JVMs, so you should avoid synchronizing between threads.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Hi,
I'd hope that the value is never null, it was just an observation. How long
is there between a *putById *and a *hasById*?
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Hi,
I think you've misunderstood warm-up requests. GAE will spin-up and
tear-down your application very often, especially if you have very little
traffic going through. The warm-up requests are simply a mechanism for
carrying out some initialisation, so that if a new instance is required to
My only two comments are:
- MemCache can contain null values - it wouldn't be the cause of your
issue but it's worth checking for null, rather than assuming that the
returned value has a length.
- Your data will never stay in MemCache for 30 days - how often are your
calls
Hi,
You can't connect GAE applications to external databases directly. The only
external connections which are allowed are connections over the HTTP
protocol.
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To
Sorry, I should also have added that GAE doesn't currently support PHP
either!
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
When you state that *As of now, there are no data store reads and writes*,
quite clearly there are datastore reads and writes somewhere in your
application - if there weren't and Google were miscalculating this, then
everyone would be up in arms.
If your application is almost working as a
You may want to raise a Production issue, if this is happening after you've
deployed the code:
http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To
I strongly suggest you read the documentation about the datastore around
querieshttp://code.google.com/appengine/docs/python/datastore/queries.html-
what you're experiencing is the eventual consistency of queries, which can
occur in Production and is highlighted in the development environment.
There isn't an issue because it was designed in - see the SDK release
noteshttp://code.google.com/p/googleappengine/wiki/SdkReleaseNotesfor 1.5.1
The eventual consistency of queries can and will happen in Production - if
you are using the High Replication datastore in Production, read all of
Have a read of the Development Server
infohttp://code.google.com/appengine/docs/java/tools/devserver.html -
this explains how to set it from both the command line or through the
Eclipse plug-in GUI.
--
You received this message because you are subscribed to the Google Groups
Google App
How are you deploying your classes? Under WEB-INF/classes, or as a custom
JAR file?
Another developer posted that they had a massive performance improvement
deploying their classes in a JAR file - see
https://groups.google.com/d/msg/google-appengine/Gl7OaMOHJD8/i_ti0KceockJ
for the relevant
You're not placing anything in your session which isn't serializable are
you?
Given that everything seems to be failing when it's starting up a new
instance, which is when it will attempt to read the session out of the
datastore/memcache, it may be that it can't deserialize your data.
--
Is this a serious question?
Your web app's WAR can just be installed into JBoss or Tomcat - then all
you'll have to do is rewrite all of your code which uses the datastore,
memcache, and any of the other GAE SDK APIs...
--
You received this message because you are subscribed to the Google
Hi,
There have been a number of issues with MemCache availability over the last
few days. You need to ensure that your code is written in such a way that
if MemCache is unavailable, your application carries on as normal (if
possible) - at the end of the day it's only a cache, not a datastore.
Hi,
According to the API docs, a* MemcacheServiceException goog_467659057*
http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/memcache/MemcacheServiceException.htmlwill
be thrown for backend non-availability or similar error states which may
occur, but are not
Hi,
Additionally, it seems you can specify the error handling you would like in
your application using the ErrorHandler
http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/memcache/ErrorHandler.htmlinterface
and the
Are you talking about static resources, or your Java compiled code? The
former can be cached on the front-end servers, so you need to use some
cache-busting techniques to get around that if you are updating static
resources. I can't say I've ever experienced issues with Java code being
I should add that, as far as I'm aware, GAE is still in beta - it is due to
come out of beta by the end of the year I believe.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
There have been a few threads discussing this recently. It appears that
they are bringing in the new instance scheduler in the background, which
will eventually replace the Always On concept. Unfortunately this has the
side effect that the current Always On instances aren't being used in the
There is no way to query a server using UDP packets on GAE - the only
supported transport protocol is HTTP.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Comments below - I'd say that the person who wrote the article did very
little research, or was using some very out of date resources, if that
article was really written in Feb this year.
On Thursday, 18 August 2011 10:57:34 UTC+1, Thomas Wiradikusuma wrote:
Hi guys,
I just stumbled upon
Hmm not sure where I got February from - replace all references to February
with April!
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Hi,
Have you tried the following on the Calendar object?
today.set(Calendar.MILLISECOND, 0);
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
It means that you will very likely require a proxy server in the middle.
GAE doesn't allow you to present a single, static IP address and all
GAE-hosted applications will be detected as the same IP range - I know for
Twitter / Facebook there have been a number of developers who have hit
A few questions / comments:
- How many instances can you see being started in your GAE application,
in the admin console? This code only works on the assumption that you have
one JVM running and it's very likely that you have more than one. i.e. To
put it bluntly, this code is
A few questions:
- Is this happening on your development or production server?
- Have you created any custom indexes?
- Also, have you turned off property indexes at all?
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine
Can you post your Entity class, with annotations, and the code for setting
up the today variable in the query? My only guess at the moment is that
the millisecond component of the date is not equal.
--
You received this message because you are subscribed to the Google Groups
Google App
Hmm, can you please check the milliseconds components of both the stored
object and your query object. You're resetting all properties of the time
apart from the milliseconds bit!
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
There is another thread for this issue, on the main GAE forum, which has
been answered by a Googler -
https://groups.google.com/d/msg/google-appengine/Zx85suFS3zc/o5SeyhH4eSkJ
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To
If that was your original code, that could definitely cause the problem -
two threads can both hit that method at the same time and create a new
PersistenceManager.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this
Whilst I don't know what could cause this error, what makes you believe that
static and static final are equivalent? Static variables are in no way
implicitly final.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this
Given that the target GAE datastore should be optimised for reads, since
writes are expensive, normalization of data is by no means the way to go.
Are Categories and Groups joined in any way? i.e. Has a specific Category
got a set of groups, or the other way around? If not, then storing the
Are you experiencing into the new functionality of the SDK, which is
emulating the eventual consistency of a High-replication datastore? This is
turned on by default in the newest SDKs - see this post for more info -
https://groups.google.com/forum/#!topic/objectify-appengine/ECNbSVgEcSQ
--
The link you've provided states that you can't use FileInputStream, as it's
not a whitelisted class.
Have you tried placing the XML file into your classes directory and using
getClass().*getResourceAsStream()?*
--
You received this message because you are subscribed to the Google Groups
Oops, read that link without any coffee! It obviously states that you *can*use
the FileInputStream class - have you tried dropping the war bit off
your filepath?
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this
Hi,
I suspect that it is because your last few posts have been asking questions
about only GWT - if you keep you GAE questions in this forum and the GWT
questions in the GWT forum, I suspect you'll get more responses!
Cheers,
Simon
--
You received this message because you are subscribed to
Hi,
What version of the SDK are you using? The increase to the time allocated
for backgrounds tasks only took place in v1.4 onwards. Also, there was a
bug in the development server pre version 1.4.3, which meant that the tasks
didn't have a 10 minute timeout.
Cheers,
Simon
--
You received
What storage mechanism are you using JPA or JDO? I'm assuming that if
you've got the error message for your Card object, that it would be a
two-minute job to test the scenario you're querying about.
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Just be warned that some users were complaining that their entities were
being flushed within seconds, a couple of months ago. I personally haven't
experienced this, however.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To
Hi,
Didier's solution will definitely do the job for servlets. Alternatively,
you could use a servlet filter to wrap all calls to specific URL mappings
that allows you to capture the same data, without the need for a common base
class, as well as capturing data for dynamic pages as well.
You
The stats are obviously completely dependent on how you write your code, the
balance between reads/writes and how much you are able to cache.
Underlying stats and fluctuations for each of the services can be seen at
http://code.google.com/status/appengine
Cheers,
Simon
--
You received this
Hi,
You could persist the users/roles in the datastore and then apply a
RequestFilter to specific URL mappings, passing in the valid roles for each
filter through an init-param of the specific filter definitions.
e.g.
filter
filter-nameallRoles/filter-name
I get datastore stats on my HR apps. They are updated every 5 or 6 hours -
is your app new?
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To
Hi,
In your first scenario, by setting a maximum of one concurrent task, unless
your tasks are taking 0.01 seconds to run you will never hit 100/s. How
long do your tasks take to run on average?
Can you paste a sample of one of your queue configurations?
Cheers,
Simon
--
You received this
Can you post the code for your MyUser and the MyImage classes as well?
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send
I've no idea whether it makes any difference, but try changing the
following:
@Persistent
private MyImage avatar;
to
@Persistent(defaultFetchGroup = true)
private MyImage avatar;
--
You received this message because you are subscribed to the Google Groups
Google App Engine
Is there any reason you make a new MyImage object? Why can't you just
change the MyImage object which already exists in the MyUser object?
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to
Hi,
In what way is it not working?
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
Hi,
I don't personally use JDO, but don't you have to re-put your object?
I don't know how JDO does its dirty checking - I doubt very much that it
will persist modified entities just because you're closing the Persistence
Manager.
Cheers,
Simon
--
You received this message because you are
If you look in the datastore admin tool, can you see whether the Recipe is
being updated with the new image reference? Are you seeing this problem on
Dev or Prod?
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this
Have you tried deploying to GAE? You can only see child fields in the
datastore viewer in Production.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To
Yes, that's what I would have expected - how else would a recipe ever retain
which image it is related to? Is the relationship purely stored within the
key of the Image?
I must admit that without any knowledge of JDO and its relationship
management, I'm just making wild guesses!
--
You
The simple answer is yes. The property index entries are created when the
entity is persisted, unlike the query indexes which are built on deployment.
I believe the advice would be to create a simple mapper job which touches all
of the entities in the background.
Cheers,
Simon
--
You
The simple answer is yes. The property index entries are created when the
entity is persisted, unlike the query indexes which are built on deployment.
I believe the advice would be to create a simple mapper job which touches all
of the entities in the background.
Cheers,
Simon
--
You
Hi,
My first bit of advice is read all of the documentation available, even if
the topic doesn't appear relevant at first, as there are little gems of
knowledge and limitations about the platform scattered throughout. I'd even
go as far as to say you would benefit from reading the Python
Static initializers will be thread-safe, but you've got to remember that
that class may be loaded in multiple JVMs, depending on how many instances
get spun up for your application.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
1 - 100 of 129 matches
Mail list logo
