[appengine-java] Stats are 0ms in AppStats
I always get 0 ms when deployed, anyone know what the issue is? real=848ms cpu=0ms api=0ms overhead=0ms (2 RPCs) -- 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-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: NullPointerException while persisting a new entity
I also had this problem, and I fixed it. I found that it occurs when you have a com.google.appengine.api.datastore.Text field, and you construct it with a null. That is, new Text(null). The workaround, if the string is null, make the text property null. On Apr 16, 4:40 pm, Coelho coelh...@gmail.com wrote: I would report the same problem and maybe help with more details. I change the primary key of a persisntant propertie of my class from String to Long, and after a lot of problems with that I, decide to get back for String type. After that my objects couldn´t be persistant anymore. Please help us!! I´m at the same situation, stucked and bored... Kind regards Coelho On 4 mar, 22:36, dantuluri pdantul...@gmail.com wrote: Hi, My app was working fine and I made few changes. Suddenly, it cannot create new entities any more. It can modify the existing entities. I reverted my changes back to where it was. Problem doesn't go away. This is in the local environment. I deleted the data file. New data file is created with other entities. But this problem still exists for the affected entity type. I attached the exception. Exception doesn't tell anything. Now I am stuck. Please help find out the root cause of this problem. Thanks, Prasad java.lang.NullPointerException at com.google.storage.onestore.v3.OnestoreEntity $PropertyValue.setStringValue(OnestoreEntity.java:1768) at com.google.appengine.api.datastore.DataTypeTranslator $TextType.setPropertyValue(DataTypeTranslator.java:737) at com.google.appengine.api.datastore.DataTypeTranslator.createProperty(DataTy peTranslator.java: 196) at com.google.appengine.api.datastore.DataTypeTranslator.addProperty(DataTypeT ranslator.java: 160) at com.google.appengine.api.datastore.DataTypeTranslator.addPropertiesToPb(Dat aTypeTranslator.java: 143) at com.google.appengine.api.datastore.EntityTranslator.convertToPb(EntityTrans lator.java: 47) at com.google.appengine.api.datastore.DatastoreServiceImpl $2.run(DatastoreServiceImpl.java:169) at com.google.appengine.api.datastore.TransactionRunner.runInTransaction(Trans actionRunner.java: 30) at com.google.appengine.api.datastore.DatastoreServiceImpl.put(DatastoreServic eImpl.java: 161) at com.google.appengine.api.datastore.DatastoreServiceImpl.put(DatastoreServic eImpl.java: 141) at com.google.appengine.api.datastore.DatastoreServiceImpl.put(DatastoreServic eImpl.java: 133) at org.datanucleus.store.appengine.RuntimeExceptionWrappingDatastoreService.pu t(RuntimeExceptionWrappingDatastoreService.java: 93) at org.datanucleus.store.appengine.DatastorePersistenceHandler.put(DatastorePe rsistenceHandler.java: 165) at org.datanucleus.store.appengine.DatastorePersistenceHandler.put(DatastorePe rsistenceHandler.java: 112) at org.datanucleus.store.appengine.DatastorePersistenceHandler.insertObjects(D atastorePersistenceHandler.java: 239) at org.datanucleus.store.appengine.DatastorePersistenceHandler.insertObject(Da tastorePersistenceHandler.java: 225) at org.datanucleus.state.JDOStateManagerImpl.internalMakePersistent(JDOStateMa nagerImpl.java: 3185) at org.datanucleus.state.JDOStateManagerImpl.makePersistent(JDOStateManagerImp l.java: 3161) at org.datanucleus.ObjectManagerImpl.persistObjectInternal(ObjectManagerImpl.j ava: 1298) at org.datanucleus.ObjectManagerImpl.persistObject(ObjectManagerImpl.java: 1175) at org.datanucleus.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceM anager.java: 669) at org.datanucleus.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceMana ger.java: 694) at com.flocle.workflow.server.data.DataStoreHelper.persistFlow(DataStoreHelper .java: 100) at com.flocle.workflow.server.dao.FlowDAOImpl.createFlow(FlowDAOImpl.java: 52) at com.flocle.workflow.server.servicebean.FlowServiceImpl.addFlow(FlowServiceI mpl.java: 88) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.google.appengine.tools.development.agent.runtime.Runtime.invoke(Runtime .java: 100) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java: 527) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServi ceServlet.java: 166) at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceSer vlet.java: 86) at
[appengine-java] Re: Datastore Limits
What do you mean by times out? Do you mean you hit the 30 second deadline? On Sep 14, 3:59 am, hg hgo...@gmail.com wrote: Hi, I am writing a script that is supposed to run quite a few inserts to the datastore - up to a couple of hundred. My script keeps timing out at 92. After I ran it a few times this evening, it wiped out my entire datastore! I did some research and came across the following error documentation: for the DatastoreTimeoutException DatastoreTimeoutException is thrown when a datastore operation times out. This can happen when you attempt to put, get, or delete too many entities or an entity with too many properties, or if the datastore is overloaded or having trouble. I was not getting this error, but it does seem to have some bearing on this case. What are the limit on entity 'putting' for a script? Any suggestions would be appreciated. Thanks! --~--~-~--~~~---~--~~ 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 google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: Performance implications of embedded classes
Embedding is the same as defining the fields on the parent. Assuming you need the embedded data most of the time, and it is small, I think you gain a performance boost as to load the data you only load one entity, not two. This assumes the embedded class is small in size, and you require its data. The data would not be lazily loaded. If you hardly use its data, or it is large and you only sometimes need it, you will loose performance as it is loaded each time. Also using embedded means you can search the parent via the embedded fields. Otherwise you cannot. On Aug 26, 7:25 am, Larry Cable larry.ca...@gmail.com wrote: I'd be surprised if you can even get them to work!!! I am having no end of trouble getting a pretyt basic @Embedded scenarios to work ... good luck! On Aug 25, 2:19 pm, fx.mueller fr.x.muel...@gmail.com wrote: Hello, I just went through the getting started documents and have a question regarding embedded classes, which I haven't found discussed elsewhere (maybe because it is trivial ;-): What are the performance implications of defining a class as embedded? Is it the same as if the fields of the embedded class are directly defined in the parent class? Or do I gain any performance benefits by defining a class as embedded - maybe because the fields of the embedded class become part of a different index? Or maybe because the fields of the embedded class are lazily retrieved if the parent class is retrieved? thanks, franz- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ 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 google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
