Hm, appengine-java-sdk-1.3.8? I think ThreadSafe was introduced with
App Engine 1.4.3
Can you test with a newer version of the SDK?
Best regards
/Dick Larsson
On 24 Okt, 08:59, Zde Sam zde...@gmail.com wrote:
Hi,
I am getting the following error after adding threadsafetrue/threadsafe
in
I'm afraid I can't answer your questions directly, but I would
sincerely suggest you look at Objectify. It offers a tidy way to
migrate to using the low level datastore - and is much easier to code.
JDO feels like a square SQL peg for the round hole of NoSQL.
On 25 October 2011 03:18, Sheado
Since that version of GAE uses an ancient version of DataNucleus, you
could simply put your update code within a transaction.
--
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
Were all the requests sent at the same time (can you check using
wireshark or similar) or did your browser queue them - most browsers
have a connections per server limit as well as a total connection
limit and some will do their best to re-use a single connection where
possible.
On 26 October
In method uploadAvatarImage you call for the inputStream before you
have sent your bytes to the server.
Please try this instead
os.flush();
os.close();
InputStream is = servletConnection.getInputStream();
Next thing, in your servlet.
You should use InputStream instead of Reader since you are
Hello Simon,
This is the callstack on exception we were getting in the JSPs, which
are not using anything memcache related:
org.apache.jasper.runtime.JspFactoryImpl internalGetPageContext:
Exception initializing page context
com.google.appengine.api.memcache.MemcacheServiceException: Memcache
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!
Thank you for your response... indeed, it was the browser that serialized
all the requests (I used both Firefox 3.x and 7.x)... I've checked the app
using wget and everything worked as expected. I didn't bother to check the
browser because I configured Firefox to use separate brand new
Have you tried adding a different query parameter to each request?
On 27 October 2011 13:53, cryb cbuti...@gmail.com wrote:
Thank you for your response... indeed, it was the browser that serialized
all the requests (I used both Firefox 3.x and 7.x)... I've checked the app
using wget and
Hi everyone,
In an application using the High Replication Datastore, the blobstore is
eventually consistent too or it is strongly consistent?
or simply:
it is possible that in the servlet called after uploading a blob this line:
Image im = ImagesServiceFactory.makeImageFromBlob(blobKey);
I've tested it and I can confirm that a dummy query parameter solves the
problem... this is mainly because Firefox perceives the newly formed urls
as separate resources... however, for the same resource I still could not
find a way to get Firefox to open concurrent connections. Meanwhile, I
Thanks for the reply Ikai, that was the information I needed.
--
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/-/85UIicBcxZQJ.
To post to
Hi,
I have been doing a lot of reading on Ancestor queries because we are
currently trying to transfer from Master / Slave to the High Replication
datastore.
We have noticed while testing on the HRDS, that sometimes when adding an
entity and redirecting the view to show that entity (or maybe
Wild guess:
If you load an entity in JDO and set a property to be exactly what it was
before, this won't actually flag the entity as dirty. It won't be written
when you commit the session. I don't know how you would force a write
using JDO.
Jeff
On Thu, Oct 13, 2011 at 6:23 AM, markabrucey
Hi Miguel,
This is an expected behavior. The other way around is also true: if your
user logout of you application, they will still be login onto their OpenID
provider.
The OpenID Provider (Identity provider) and your application (relying
party) do not know each others, The OpenID provider
HI
I'm getting
Nested in javax.servlet.ServletException:
java.lang.ClassCastException: cannot assign instance of
java.lang.String to field dr.todo.beans.ToBuyBean.quantityToAdd of
type java.lang.Integer in instance of dr.todo.beans.ToBuyBean:
cause I had a String and now i changed it to Integer
Guys anyone any ideas on this please?
On 24/10/2011 13:47, Tom Fennelly wrote:
Hi all.
I searched the archives but was unable to find an answer to my
question. Basically wondering if it's possible to programatically
create an application instance. Obviously I can update an instance
Yes, thank you very much Jose: you are very useful! You perfectly got
the point I didn't understand correctly .. ;)
But now I have to think about the solution .. I would propose this
one:
I have always to rely on the session (and not on the UserService); if
there is no session active I propose to
Yes, you can, using WebDriver.
I don't remember if theres any captcha... that would be a problem.
Just emulate what you would do manually.
Regards
On Thu, Oct 27, 2011 at 6:18 PM, Tom Fennelly tom.fenne...@gmail.comwrote:
Guys anyone any ideas on this please?
On 24/10/2011 13:47, Tom
19 matches
Mail list logo
