Hi,
I've managed to use JSF 2 quite well with PrimeFaces. In config files I'm
using the configuration for JSF + App Engine found in many tutorials and I'm
using Client as state saving method. For libraries I'm using
Mojarra-2.1.2-FCS, Primefaces-2-2.RC1-SNAPSHOT and JSTL 1.1.
I had problems wit
And I should add that the app is up again. Seems like there were problems
starting a new instance for some reason.
--
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
I can see the same happening with my app too. It was down for couple of
minutes, lots of requests coming and getting 500 error. No instances where
shown running, every now and then there was 1 instance for 1 request but it
died away soon.
In the server logs I saw at least this which I haven't
Looks like the limit has been raised! Haven't tested yet what is the higher
limit but I have an instance with almost 19000 requests so it has been more
than doubled, at least. Good news!
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" g
Thank you! This is very good news, and gives motivation to optimize the code
to run fast :)
--
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
Thank you! I didn't know about this and tried to search (also on these
forums).
In my production app I get instance restart every 6 minutes, that's 10 times
per hour! I think I should "de-optimize" my code to run slower to make GAE
to use more instances with my current load, so my users wouldn
Hi,
I've been testing possible memory leak in my app using JDO. I created a
small app with two servlets, the other servlet creating one small JDO entity
and the other servlet creating an entity with Objectify. Running the test
with JMeter I've realised the memory usage grows quite a bit when us
Hi,
I've also seen similar errors and I'm not sure why. Using JSF 2 it happens
quite often for ajax requests. I also have another issue and I'm not sure if
it's related to the same problem. The other issue is with jsf session beans.
If you're using client-side state saving and set some value to
The datanucleus issue has a comment "Then, when my tasks run in parallel,
initialisation has already been done and the problem doesn't appear any
more.", so before the threadsafe property, only tasks were run in parallel.
Probably that's why I didn't see this error before, I didn't have tasks
d
Based on your experience it seems to be that the problem is in the access to
PersistenceManagerFactory.getPersistenceManager()? If your PMF-class fixes
the problem, then it seems that call to getPersistenceManager() should be
synchronized in multithreaded apps.
Can anyone confirm this?
I found
> use the factory method?
>
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> Blog: http://googleappengine.blogspot.com
> Twitter: http://twitter.com/app_engine
> Reddit: http://www.reddit.com/r/appengine
>
>
>
> On Thu, May 12, 2011 at 1:47 AM, J
java.io.IOException: Error posting to URL:
> https://appengine.google.com/api/appversion/create?app_id=vph-epr
> &version=6&
>
> *But*, it's exist now. http://vph-erp.appspot.com
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java
I've been running an application successfully for some time on the app
engine. During last week I've couple of times tried enabling threadsafe in
my app. It seems to randomly cause issues with retrieving or storing data
with JDO. What I see when I start to get these issues is this (I've replaced
13 matches
Mail list logo
