Hi Roberto,
@ElementCollection annotation have to be used to contain embedded entities,
therefore you're have to be sure that PositioningType class is annotated
with @Embeddable.
The next example works fine for me:
//Class Product
@ElementCollection(fetch = FetchType.EAGER)
public SetRate
Hi,
A very nice tool for developing services over appengine in java is
playframework. It has a module to work on appengine and for persistence
layer I like siena module. You can use another orm like objetify but to
start quickly siena is better.
Regards
El 27/08/2012 20:30, YulianaGH
Hi,
Safely you've exceed the backend's memory.
2011/11/18 Andrius A andriu...@gmail.com
I am running backend started by the task which starts a loop within a
backend to keep it running.
I am constantly seeing backend restarting recently, no exceptions visible
on the logs apart from these
I've been getting a lot of 500 errors too.
Eduardo
2011/5/5 Francois Masurel f.masu...@gmail.com
Getting quite a few 500 errors today.
Am I the only one ?
Francois
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this
:05, Eduardo Perrino eduardo.perr...@gmail.com
wrote:
2011/5/3 Geoffrey Spear geoffsp...@gmail.com
On May 3, 11:55 am, Eduardo Perrino eduardo.perr...@gmail.com wrote:
Hi Robert,
I try to explain better:
Our application has 16 instances assigned by appengine automatically
Thank you!!
But we are using now concurrent requests and the problem persists.
2011/5/4 Stephen sdeasey+gro...@gmail.com
Try this:
http://code.google.com/appengine/docs/java/config/appconfig.html#Using_Concurrent_Requests
Hopefully you will end up with fewer, warmer instances.
--
You
Hi!!
We have problems with the instance feature of appengine. Today we have
got 16 instances, and we've detected that many of them when receive a
request, it has to start the application again. So our application
consumes a lot of cpu because our startup process is a little heavy.
To solve this
based on the information you've provided (for me at
least).
Also, if you don't get any good insights here, try searching /
asking on the google-appengine-java group.
Robert
On Tue, May 3, 2011 at 09:59, Eduardo Perrino eduardo.perr...@gmail.com
wrote:
Hi!!
We have problems
2011/5/3 Geoffrey Spear geoffsp...@gmail.com
On May 3, 11:55 am, Eduardo Perrino eduardo.perr...@gmail.com wrote:
Hi Robert,
I try to explain better:
Our application has 16 instances assigned by appengine automatically and
three of them are always on. It doesn't have many requests
receive a 403 http error code from the api.
I need help to fix the problem.
Thanks!!
Regards.
Eduardo Perrino
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
out of the way and execute.
Doesn't your cron job have to fire every second in order to keep the
application alive? I thought that 1 request per second is the keep-
alive boundary. It's somewhere around there. How often does your cron
execute?
On Jun 16, 5:51 am, Eduardo Perrino eduardo.perr
I need help my application show the next error:
Request was aborted after waiting too long to attempt to service your
request. This may happen sporadically when the App Engine serving
cluster is under unexpectedly high or uneven load. If you see this
message frequently, please contact the App
12 matches
Mail list logo
