It is also worth noting that the object never persist on my local
computer running from eclipse debug, but there are no errors.


This is the class with functions removed:

@PersistenceCapable(identityType = IdentityType.APPLICATION)
public class Stock {
    @PrimaryKey
    @Persistent(valueStrategy = IdGeneratorStrategy.IDENTITY)
        private Key key;

    @Persistent
    private Key portfolio;

    @Persistent
    private String exchange;
    @Persistent
    private String ticker;
    @Persistent
    private String name;
    @Persistent
    private double price;
        @Persistent
        private long sharesOutstanding;
    @Persistent
    private double marketCap;
    @Persistent
    private double volume3Month;

        @Persistent
    private Vector<BalanceSheet> balanceSheets;


    @Persistent
    private Vector<IncomeStatement> incomeStatements;

  ......

}



On Sep 30, 10:02 pm, Kevin <kevinyangwater...@gmail.com> wrote:
> Mine involves adding new objects to go DB, not modifying an exist
> object. I did more testing, its seems that after a couple of hours of
> not using the application, and then coming back to it to add new
> objects to the db the objects just don't persist, I have to try a keep
> on trying to add it for like 20 minutes before it appears. Then, soon
> after persist work fine the first time I try to add objects. It is
> like I have to warm up the application before it performs at 100%.
>
> On Sep 29, 7:19 pm, orig <byoun...@yahoo.com> wrote:
>
> > I have experienced the same thing. If I create an entity, I can not go
> > back and modify a property of that entity for 15-20 minutes. It fails
> > without error. After that time it can be modified. Simple changes of
> > short strings stored in properties fail. The question is is it running
> > up against some short term quota or is it some weird contention issue.
> > The problem is seen in simple entities with basic properties.
>
> > Problem is there are many such bugs. Ever try to run a query with
> > order by and each time you get back a different result set:
>
> >http://code.google.com/p/googleappengine/issues/detail?id=901&q=query...
>
> > Funny that things like this have been around for almost a year and are
> > never addressed..... It is more important to add unused junk features
> > than fix basic issues
>
> > On Sep 29, 1:49 pm, Kevin <kevinyangwater...@gmail.com> wrote:
>
> > > Hello,
>
> > > I have an application where sometimes the object gets stores
> > > successfully to the data store and sometimes it doesn't.
> > > If I try like a couple of hours later it will work without touch
> > > anything on my application.
>
> > > I don't see any errors or warning and it definately is call the
> > > persist function. So I have indiction of what went wrong.
>
> > > Anyone experiance this before?
>
> > > Thanks in advance,
> > > Kevin.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to