I dont know, but have you examined the GAE log?

2012/3/6 Sushant Taneja <[email protected]>:
> Hi,
>
> I thought the same but as you can see I have handled the Timeout exception
> in the code.
> If its the Timeout then why I am unable to catch the exception ?
>
> On Tuesday, March 6, 2012 7:30:38 PM UTC+5:30, yamandu wrote:
>>
>> Looks its a timeout.
>> Maybe I am wrong but you can state an update too many records. GAE has
>> time limitations, I dont know how much because I dont use it anymore.
>> Search for the GAE docs on these limitations.
>>
>> 2012/3/6 Sushant Taneja <[email protected]>:
>> > Hi All,
>> >
>> > I am building a invite module.
>> > In the controller, I have the following code :
>> >
>> > try:
>> > .... some initial stuff
>> >
>> >    try:
>> >
>> >        ... some stuff
>> >
>> >        update_request_query = (db.INVITE_SIGNUP.email_id ==
>> > request_email_id)
>> >
>> >
>> >  db(update_request_query).update(activation_key=key,activation_url=activation_url)
>> >
>> >         ... some other stuff
>> >
>> >    except (Timeout,TransactionFailedError,InternalError), derr:
>> >                     logger.warn('Datastore exception for ID: '+
>> > request_email_id +': '+ str(derr))
>> > except (Error, Exception), ex:
>> >             logger.error('Fatal Error: '+ request_email_id +': '+
>> > str(ex))
>> >
>> > The problem is that the update statement is not working on GAE. The
>> > fields
>> > which need to be updated are NULL and no error is thrown.
>> > From my observation, this is happening once a day approx around the time
>> > when daily quota is reset.
>> >
>> > Am I doing something wrong here ?
>> >
>> > Thanks,
>> > Sushant
>> >
>> >
>>
>> --
>> Carlos J. Costa
>> Cientista da Computação
>> Esp. Gestão em Telecom
>>
>> EL MELECH NEEMAN!
>> אָמֵן



-- 
Carlos J. Costa
Cientista da Computação
Esp. Gestão em Telecom

EL MELECH NEEMAN!
אָמֵן

Reply via email to