Thank you so much, Vinny..
Info was very helpful :-)
Regards,
Sreekaanth
On Wednesday, 11 December 2013 09:28:04 UTC+8, Vinny P wrote:
>
> On Sat, Dec 7, 2013 at 1:10 AM, Sree >
> wrote:
>
>> I have an understanding as the project application in cloud console is
>> app engine (samplename.appsp
Hi Kris,
I will definitely look into objectify and I really appreciate your help.
Thank you so much.
On Thu, Dec 12, 2013 at 12:54 AM, Kristopher Giesing wrote:
> I'd strongly recommend Objectify as a persistence layer. It's designed
> for App Engine and works very well in my experience. Mem
Problem mysteriously resolved. I replicated it a couple of more times,
then logged out and went away for while. When I came back & logged in,
everything behaved as it should.
Go figure.
Cheers,
--Ken
--
You received this message because you are subscribed to the Google Groups
"Google App En
Hi team,
We are a premier customer of google app engine. We are planning to add more
features in our product which requires more number of datastore indexes for
that will exceed the daily quota details. Can someone please advise if the
datastore index quota can be increased on request to google
I was just working on a problem that has the same symptoms, but happened
consistently every time (on Chrome). The problem turned out to be that the
Disconnect plugin was overzealously blocking any Google API stuff,
including the talkgadget URL.
Just thought I'd mention it for anyone who has the
I have a project which is currently set for free. I'm trying to turn on
Billing, but cannot. I am an Owner and Billing Administrator of the
project. If I go to Billing > Billing Status, and click Enable Billing, I
get the page for setting budgets. However, when I click Submit on that
page,
Spoke too soon. The stack trace was from a misguided attempt to correct a
benign warning.
Still getting error 121 with no stack trace.
On Wednesday, December 11, 2013 4:37:00 PM UTC-8, Michael Collins wrote:
>
> I did just start getting a stack trace with the error 121, that should
> help, if
I did just start getting a stack trace with the error 121, that should
help, if somebody fixed something thanks...
On Wednesday, December 11, 2013 3:31:01 PM UTC-8, Francois Masurel wrote:
>
> Hi Michael,
>
> I have exactly the same problem with one of my Java app at the moment
> (bblcts2).
>
>
On Wed, Dec 11, 2013 at 2:33 AM, Ananthakrishnan Venkatasubramanian <
ananthakrishnan.venkatasubraman...@a-cti.com> wrote:
> Libraries will increase the size of the application or the parent module
> if you opt for modules. Deploying the app with libraries is old
> fashion...Its not good to follow
The errors went away after adding more logging and reuploading my code. The
logging didn't reveal anything but I guess it must be my code that caused
the problems some how.
On Wednesday, December 11, 2013 7:59:01 PM UTC, Dan wrote:
>
> I'm currently experiencing an increased error rate of 1.6% o
You need to specify the php-cgi binary, not the PHP binary
On Tuesday, 10 December 2013 20:02:33 UTC-8, Vinny P wrote:
>
> On Fri, Dec 6, 2013 at 7:10 PM, Jefrey Sobreira
>
> > wrote:
>
>> *The path specified with the --php_executable_path flag () does not
>> exist.*
>>
> So I changed the comm
Hi Michael,
I have exactly the same problem with one of my Java app at the moment
(bblcts2).
I had the same problem yesterday on another app and it lasted for more than
2 hours. It's now fixed.
François
On Wednesday, December 11, 2013 11:38:22 PM UTC+1, Michael Collins wrote:
>
> I have been
I have been working on an app for the last 5 days, all was fine until this
morning. Since then I'm getting nothing but "Error code 121" for requests
coming from my Android devices. Web pages are being served properly.
Tried rolling back to a previous working version of the device and server
co
Same here four several java apps: prncts2 (a few hours ago) and bblcts2
recently.
Hey Google, what's going on? Preparing the next update?
On Thursday, December 5, 2013 11:17:17 PM UTC+1, Rik wrote:
>
> Getting a lot of 500s with this error:
>
> A problem was encountered with the process that
I'm currently experiencing an increased error rate of 1.6% of requests and
new instance startup on almost every request. I see the elevated error rate
has been going for over 12 hours. The errors are:
> A problem was encountered with the process that handled this request, causing
> it to exit
I'd strongly recommend Objectify as a persistence layer. It's designed for
App Engine and works very well in my experience. Memcache caching is very
easy to enable, nearly transparently.
http://code.google.com/p/objectify-appengine/
- Kris
On Wednesday, December 11, 2013 5:51:19 AM UTC-8, Ja
The whole custom domain is extremely complicated.
I have written in the past that “PaaS makes many difficult things easy and a
few easy things difficult or impossible”.
Google AppEngine custom domains and SSL support is an example of the latter. I
am still hopeful that Google will listen but a
On Tuesday, December 10, 2013 6:36:35 PM UTC-8, Vinny P wrote:
>
> On Fri, Dec 6, 2013 at 2:13 PM, Martin Liersch
>
> > wrote:
>
>> Except for 2) The quota exploded! After just some hours of using this
>> setting I sais that I have used 18 "Gbyte Hours" already. How is that
>> possible, the tot
When I look at https://code.google.com/status/appengine I see that Python's
Dynamic HTTP Get Latency hovers around 10ms and is fairly stable. However
Go's hovers around 20ms and is much more erratic. Looking back on previous
days I see the situation is sometimes worse for Go.
I expected the Go
We were getting a lot of these errors and eventually noticed that they were
all happening on a particular instance(instance #19 for us). By deleting
the backend that the errors were occurring on and then bringing it back up
the issue was put to rest.
--
You received this message because you
Yeah thank you so much Nick. I am going to deploy to a new app and hence
can temporarily be safe :)
I think the problem can be avoided by using memcache instead of querying
datastore, because app will be subjected to some heavy loads.
On Wed, Dec 11, 2013 at 6:13 PM, Nickolas Daskalou wrote:
>
HI Jaya,
This is a free app with limited Datastore quota. You will need to enable
billing for further use.
On Wednesday, 11 December 2013 13:30:27 UTC+1, Jayakrishnan wrote:
>
>
>
>
> On Wed, Dec 11, 2013 at 5:59 PM, Jayakrishnan
> > wrote:
>
>>
>>
>>
>> On Wed, Dec 11, 2013 at 5:56 PM, Jayak
You've used up your daily free quota for datastore reads.
The free quotas reset every 24 hours, and it looks you are still 20 hours
away from a reset.
If you need to get your app working before then, you will need to enable
billing on this app, or alternatively, be cheeky and deploy to a new app
On Wed, Dec 11, 2013 at 5:56 PM, Jayakrishnan wrote:
> Forgot to attach file
> PFA
>
>
> On Wed, Dec 11, 2013 at 5:56 PM, Jayakrishnan wrote:
>
>> Hi,
>>
>> I get the below error while I try to enter my website,
>> The API call datastore_v3.RunQuery() required more quota than is
>> available.
>>
Hi,
I get the below error while I try to enter my website,
The API call datastore_v3.RunQuery() required more quota than is available.
Also please find the attached screenshot of my appengine console.
What do these logs tell me? When can my site go up again?
The situation is worse since I have a
Hi,
FYI: As you have suggested, we deployed the Server B as backend module and
Server A as frontend module in the same App ID and used URLFetch in module
A(Server A) to communicate with module B (Server B) of the same app. Still
the same problem for one user who is using the application and tha
26 matches
Mail list logo
