Re: [google-appengine] Re: Using @ElementCollection to persist a Collection of Enum

2012-08-31 Thread Eduardo Perrino
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 rates;

//Class Rate
@Embeddable
public class Rate {
   public String name;
}


Regards.


2012/8/30 roberto_sc roberto.cal...@gmail.com

 No opinions at all? Does it look like that I'm doing the right thing?
 I just found out that it also doesn't work for a list of integers,
 possibly any collection of any simple type:

 @ElementCollection
 @Extension(vendorName = datanucleus, key = gae.unindexed, value = true)
 //private ListPositioningType bestPositionings = new 
 ArrayListPositioningType();
 private ListInteger bestPositionings;


 Results in:

 Caused by: org.datanucleus.exceptions.NucleusUserException: The MetaData for 
 the element class java.lang.Integer of the collection field 
 com.olympya.datamodel.model.Player.bestPositionings was not found.

 at 
 com.google.appengine.datanucleus.scostore.AbstractFKStore.init(AbstractFKStore.java:120)

 at 
 com.google.appengine.datanucleus.scostore.FKListStore.init(FKListStore.java:83)

 at 
 com.google.appengine.datanucleus.DatastoreManager.newFKListStore(DatastoreManager.java:472)

 at 
 org.datanucleus.store.mapped.MappedStoreManager.getBackingStoreForCollection(MappedStoreManager.java:798)

 at 
 org.datanucleus.store.mapped.MappedStoreManager.getBackingStoreForField(MappedStoreManager.java:709)

 at org.datanucleus.store.types.sco.backed.ArrayList.init(ArrayList.java:99)


 :(

 Em quarta-feira, 29 de agosto de 2012 13h46min03s UTC-3, roberto_sc
 escreveu:


 I'm moving from JPA 1 to JPA 2 in my Gooogle App Engine project, and for
 that I changed the annotations for collections of enums, like this case:

 //  @OneToMany(cascade = CascadeType.ALL) // JPA 1
 @ElementCollection(targetClass**=PositioningType.class)

 private ListPositioningType bestPositionings;


 PositioningType is an enum that is not annotated.

 That code is giving me the following exception:

 javax.persistence.PersistenceE**xception: The MetaData for the element class 
 com.olympya.datamodel.model.**PositioningType of the collection field 
 com.olympya.datamodel.model.**Player.bestPositionings was not found.

 at 
 org.datanucleus.api.jpa.Nucleu**sJPAHelper.getJPAExceptionForN**ucleusException(NucleusJPAHelp**er.java:302)

 at 
 org.datanucleus.api.jpa.JPAEnt**ityTransaction.commit(JPAEntit**yTransaction.java:122)

 at com.olympya.Services.mergeUser**(Services.java:102)
 ...
 Caused by: org.datanucleus.exceptions.Nuc**leusUserException: The MetaData 
 for the element class com.olympya.datamodel.model.**PositioningType of the 
 collection field com.olympya.datamodel.model.**Player.bestPositionings was 
 not found.

 at 
 com.google.appengine.datanucle**us.scostore.AbstractFKStore.i**nit(AbstractFKStore.java:120)

 at 
 com.google.appengine.datanucle**us.scostore.FKListStore.init**(FKListStore.java:83)

 at 
 com.google.appengine.datanucle**us.DatastoreManager.newFKListS**tore(DatastoreManager.java:472**)

 at 
 org.datanucleus.store.mapped.M**appedStoreManager.getBackingSt**oreForCollection(MappedStoreMa**nager.java:798)

 at 
 org.datanucleus.store.mapped.M**appedStoreManager.getBackingSt**oreForField(MappedStoreManager**.java:709)

 at 
 org.datanucleus.store.types.sc**o.backed.ArrayList.init(Arra**yList.java:99)

 at sun.reflect.NativeConstructorA**ccessorImpl.newInstance0(Nativ**e Method)
 ...

  --
 You received this message because you are subscribed to the Google Groups
 Google App Engine group.
 To view this discussion on the web visit
 https://groups.google.com/d/msg/google-appengine/-/M9bihLLrsTAJ.

 To post to this group, send email to google-appengine@googlegroups.com.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.


-- 
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.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] Services in App Engine

2012-08-27 Thread Eduardo Perrino
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 ygar...@adquem.com escribió:

 Hello, I wonder how to implement services on App engine, using the Java
 language. If existing a API, someone that a give me a procedure or example
  for implement in a simple projec. Thanks

 Sorry for my english.

 --
 You received this message because you are subscribed to the Google Groups
 Google App Engine group.
 To view this discussion on the web visit
 https://groups.google.com/d/msg/google-appengine/-/WWhdF6A3D_cJ.
 To post to this group, send email to google-appengine@googlegroups.com.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.



-- 
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.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] Please Help! Backend restarts every few hours

2011-11-18 Thread Eduardo Perrino
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 errors:



1.  2011-11-18 09:36:38.480 /app/executor/master/ 500 3654275ms 0kb
instance=0 AppEngine-Google; (+http://code.google.com/appengine)

0.1.0.2 - - [18/Nov/2011:01:36:38 -0800] POST /app/executor/master/ 
 HTTP/1.1 500 0 http://0.master-executor.xxx.appspot.com/_ah/start; 
 AppEngine-Google; (+http://code.google.com/appengine) 
 master-executor.xxx.appspot.com ms=3654275 cpu_ms=5810488 
 api_cpu_ms=3602612 cpm_usd=100.072612 queue_name=master-executor-queue 
 task_name=master-executor-job-1321599921 exit_code=109 instance=0

2.  E2011-11-18 09:36:37.596


Connection to client lost.


What does exit_code=109 means?


Thanks for your help!


  --
 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.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.


-- 
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.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] Error 500

2011-05-05 Thread Eduardo Perrino
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 group, send email to google-appengine@googlegroups.com.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.


-- 
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.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] Re: Instances

2011-05-04 Thread Eduardo Perrino
Hi Robert,

After all, thank you for your recomendation of use Appstats. I'm going to
use it.

Undeploy application doesn't mean lose an instance because I see a lots of
loading request in my logs. We've developed a warm up servlet to start up
the application into dynamic instances when I've activated always on
feature. But we've detected into always on instances that the application is
shutting down too.

Also I think the algorithm for dispatching requests between instances is
Round Robin and when we haven't got requests enough. So we've got a lot of
loading requests because the time between requests into the same instance is
long enough to shut down the application for appengine.

Eduardo.

2011/5/4 Robert Kluin robert.kl...@gmail.com

 Hi Eduardo,
  It sounds like you might benefit from using Appstats.  I've heard
 Java apps tend to have large startup times. However, from what you're
 describing it sounds like your app is getting new instances spun up
 (16 in total) but it is not serving requests quickly enough.  At least
 if I understand the issues correctly.

  http://code.google.com/appengine/docs/java/tools/appstats.html

  When you say 'undeploy' the application, you mean you lose an
 instance?  As in you go from, say, 16 to 15 instances?  Also what
 Geoffrey said is correct (of course ;), only active instances are
 listed.  Instances can be spun up and down at any time.  Do you see
 lots of loading requests in your logs?



 Robert





 On Tue, May 3, 2011 at 13: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
 and
   three of them are always on. It doesn't have many requests, in fact,
   the
   time between them is large enough to appengine undeploy the
 application.
   So
   appengine is starting the application over and over.
 
  If the Instances section of the control panel shows that you currently
  have 16 instances, that's how many copies of your application are
  currently running. Instances that are undeployed, as you put it,
  won't show in that panel.
 
  This is not true, because sometimes when an instance has received a
 request
  the latency time is increased very much and if you go to the logs section
  it's posible to see that the application has been started.
 
  I think, see the instances is not mean that the application is started.
 
 
 
  --
  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.
  To unsubscribe from this group, send email to
  google-appengine+unsubscr...@googlegroups.com.
  For more options, visit this group at
  http://groups.google.com/group/google-appengine?hl=en.
 
 
  --
  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.
  To unsubscribe from this group, send email to
  google-appengine+unsubscr...@googlegroups.com.
  For more options, visit this group at
  http://groups.google.com/group/google-appengine?hl=en.
 

 --
 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.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.



-- 
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.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] Instances

2011-05-04 Thread Eduardo Perrino
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 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.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.



-- 
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.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



[google-appengine] Instances

2011-05-03 Thread Eduardo Perrino
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 situation we've enabled always on feature, and the
problem becomes bigger, because always on instances has to start the
application too.

We don't understand this behavior and we need help to solve this.
Otherwise we'll have to stop using appengine as a valid JAVA
development platform because stop and start in every moment the
application is unacceptable into this enviroment.


Eduardo

-- 
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.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] Instances

2011-05-03 Thread Eduardo Perrino
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, in fact, the
time between them is large enough to appengine undeploy the application. So
appengine is starting the application over and over.

Our application is java based and we're using spring MVC, Security, IoC and
AOP, we've optimized the startup of it to reduce this time, more or less the
startup time is not exceed more than 15 seconds.

I've attached screenshot to show the instances's status.

Thanks for your interesting.

Eduardo.



2011/5/3 Robert Kluin robert.kl...@gmail.com

 Hi Eduardo,
  Perhaps you could explain we've detected that many of them when
 receive a request, it has to start the application again more
 precisely.  It is rather hard to give any advise other than make your
 app startup faster 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 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 situation we've enabled always on feature, and the
  problem becomes bigger, because always on instances has to start the
  application too.
 
  We don't understand this behavior and we need help to solve this.
  Otherwise we'll have to stop using appengine as a valid JAVA
  development platform because stop and start in every moment the
  application is unacceptable into this enviroment.
 
 
  Eduardo
 
  --
  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.
  To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.com.
  For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.
 
 

 --
 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.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.



-- 
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.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] Re: Instances

2011-05-03 Thread Eduardo Perrino
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, in fact,
 the
  time between them is large enough to appengine undeploy the application.
 So
  appengine is starting the application over and over.

 If the Instances section of the control panel shows that you currently
 have 16 instances, that's how many copies of your application are
 currently running. Instances that are undeployed, as you put it,
 won't show in that panel.


This is not true, because sometimes when an instance has received a request
the latency time is increased very much and if you go to the logs section
it's posible to see that the application has been started.

I think, see the instances is not mean that the application is started.




 --
 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.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.



-- 
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.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



[google-appengine] google api client and google url shortener

2011-04-24 Thread Eduardo Perrino
Hi,

I'm using google-api-java-client-1.3.2-alpha to use google's url
shortener api. I've configured correctly the api in the console api
and I'm using the api without problems in development server. But when
I deploy the aplication into appengine production enviroment and I try
to use the api I 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.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] Re: Request was aborted after waiting too long to attempt to service your request

2010-06-17 Thread Eduardo Perrino
My cron runs every minute because it is the minimal period that gae
supports.



2010/6/16 Tristan tristan.slomin...@gmail.com

 From my understanding this error happens when a request hits an
 application instance but is put on a queue and becomes stale before
 other requests in front of it get 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...@gmail.com wrote:
  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 Engine team.
 
  I created a cron job to keep alive the application, but the error
  persits, i need help to fix it.
 
  Thanks

 --
 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-appeng...@googlegroups.com.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.



-- 
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-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



[google-appengine] Request was aborted after waiting too long to attempt to service your request

2010-06-16 Thread Eduardo Perrino
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 Engine team.

I created a cron job to keep alive the application, but the error
persits, i need help to fix it.

Thanks

-- 
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-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.