[google-appengine] Re: deploy is very slow

[Luis F De Pombo]

Hi Nick,
I am having the same issue as Adam but I am using a nodejs Flex env. I have 
the file you point to, what is the best email to get this to you? Thank you.

On Monday, February 6, 2017 at 10:40:48 AM UTC-8, Nick (Cloud Platform 
Support) wrote:
>
> Just a quick update:
>
> As well, to avoid the timestamp filtering commands above, you could simply 
> run the deployment with the --verbosity debug and --log-http flags and then 
> run gcloud info to check for where the "latest log file" is stored, and 
> upload that file. The output line telling its location will look like:
>
> Last Log File: [/home/anon/.config/gcloud/logs/2017.02.06/18.30.49.455744.log]
>
>
> On Monday, February 6, 2017 at 12:58:05 PM UTC-5, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Adam,
>>
>> Could you capture the deployment logs using the flags "--verbosity debug" 
>> and "--log-http", piping this output into the "ts" utility to prepend a 
>> timestamp to each line, and then email me the logs? I'll be able to analyze 
>> what might be going on that way. On linux / Mac that will look like:
>>
>> gcloud --quiet --verbosity debug --log-http app deploy app.yaml --version 
>> ${VERSION} 2>&1 | ts | tee -a deploy_log.txt 
>>
>>
>> (tee is used so that you can still read the output as it hits the 
>> console, and note that you'll have to put whatever version you want in the 
>> command where ${VERSION} is written)
>>
>> On windows, you can use powershell to run the same command line after 
>> creating the "ts" filter to prepend timestamps by running the following 
>> line:
>>
>> filter timestamp {"$(Get-Date -Format s): $_"}
>>
>>
>> Cheers,
>>
>> Nick 
>>
>> On Saturday, February 4, 2017 at 2:30:00 AM UTC-5, Adam Mathias 
>> Bittlingmayer wrote:
>>>
>>> Yes, it is the Flex Env.
>>>
>>> Reviewing the container build logs, it does not seem deterministic.  The 
>>> total time varies, and the place in the process where multiple minutes pass 
>>> between two log lines varies.
>>>
>>>
>>> On Friday, 3 February 2017 12:40:25 UTC-8, Nick (Cloud Platform Support) 
>>> wrote:

 Hey Adam,

 Are you deploying a Flexible Environment app? If so, what do the 
 container builder logs from the Console show as far as activity during 
 this 
 time?

 Also, is this still occurring, or was it only for a certain period of 
 time? If it's transient, it might just be a momentary service degradation, 
 which for a Beta product is to be expected at this stage. When a product 
 goes into General Availability, we'll often have certain Service Level 
 targets in terms of latency, uptime, that you can rely on (for example, 
 read 
 here  for Compute Engine SLA's)

 Cheers,

 Nick
 Cloud Platform Community Support

 On Thursday, February 2, 2017 at 9:02:29 AM UTC-5, Adam Mathias 
 Bittlingmayer wrote:
>
> Deployment with gcloud deploy app is slow (in the low dozens of 
> minutes).
>
> The build is fast, it is the push steps that are slow.
>
> Both steps like Mounted from google_appengine/python and Updating 
> service [test]...\ ie steps that are in the datacentre, not the 
> upload itself.
>
> Thus the size of the code seems to have no effect, it is small enough 
> in this case.  It happens with both python 2 and 3.
>
> Is there a way to increase an allocation to speed this up?  Are there 
> other factors?
>


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/47f0bc40-1427-4db7-bd62-fb7e07a858d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Task Queue Hang and Do not have a way to purge tasks inside

[Christian F. Howes]

FYI - I had the same issue happen to me last friday.  I sent feedback from 
the page and have shared a HAR log with someone on the task queues team.  
it feels to me like there are problems when the queue size gets to be in 
the thousands and the execution rate is fast - when my queue got smaller i 
was able to access it again.

cfh

On Monday, August 8, 2016 at 8:34:55 AM UTC-7, Nicholas (Google Cloud 
Support) wrote:
>
> Thank you for responding to me privately.  I'm glad to hear you are no 
> longer encountering this issue and that it seemed transient.
>
> Should this error present itself again, I would strongly suggest filing a 
> defect report on the App Engine public issue tracker 
>  and attaching a HAR 
> capture  of Developer 
> Console network requests when seeing the *Failed to load* message.  Happy 
> coding!
>
> On Monday, July 25, 2016 at 9:41:38 AM UTC-4, Roy Yeung wrote:
>>
>> I have two PULL queues that hangs and some tasks accumulated.
>>
>> I want to purge and delete the queue.
>>
>> However, it show "Failed to load" when i click on the pull queue's name. 
>>
>> Anyone have idea ?  
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d0360261-53aa-4b69-bdd1-0ca4a82b583d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Frontend inconsistent caching

[Christian F. Howes]

While we have not tried this with flexible runtimes, on standard GAE we are 
using cache-control, and pragma headers.  we do not use the vary header.  
while not documented the GAE support folks confirmed that google's caching 
proxy will not cache responses with certain values for the vary header 
(like custom headers and language headers), so you might try removing that 
from both systems.

also last i checked the cache was not guaranteed, and it's possible if your 
second app has low traffic that it's deemed not worth caching?  this area 
is a black box to me.

cfh

On Wednesday, August 3, 2016 at 4:34:11 PM UTC-7, Nick (Cloud Platform 
Support) wrote:
>
> Hey Matt,
>
> This is very interesting, and although I'd almost say it qualifies for a 
> post to the Public Issue Tracker, we can also discuss it here, since it's 
> somewhat broad, and it would be inconvenient to migrate all this info.
>
> Are you making your requests from behind any kind of proxy? This is 
> something which comes to mind. 
>
> I'll see if we can see anything from our end in the meantime.
>
> Cheers!
>
> Nick
> Cloud Platform Community Support
>
> On Monday, August 1, 2016 at 11:22:16 AM UTC-4, Matt Mohebbi wrote:
>>
>> I have a nodejs application I deploy to Appengine Flexible Environment 
>> via a docker custom runtime. When I deploy to one project (iodine-test), I 
>> get the great caching features of the Google Frontend:
>>
>> air:/tmp/plum/deploy-20160727-124350% curl -w 
>> "@/Users/matt/bin/curl-time-format.txt" -o /dev/null -s "
>> http://iodine-test.appspot.com/drug/zoloft; -v
>>
>> *   Trying 216.58.194.209...
>>
>> * Connected to iodine-test.appspot.com (216.58.194.209) port 80 (#0)
>>
>> > GET /drug/zoloft HTTP/1.1
>>
>> > Host: iodine-test.appspot.com
>>
>> > User-Agent: curl/7.43.0
>>
>> > Accept: */*
>>
>> > 
>>
>> < HTTP/1.1 200 OK
>>
>> < Content-Type: text/html; charset=utf-8
>>
>> < ETag: W/"30a48-XHteNhi+a5i5072zCcVDyg"
>>
>> < Vary: Accept-Encoding
>>
>> < Via: irbk129:14580
>>
>> < X-Cloud-Trace-Context: 02917deaade7c823eed970361cd13ded;o=1
>>
>> < Date: Mon, 01 Aug 2016 15:15:49 GMT
>>
>> < Server: Google Frontend
>>
>> < Content-Length: 199240
>>
>> < Cache-Control: public, max-age=604800
>>
>> < Age: 7
>>
>> < 
>>
>> { [6754 bytes data]
>>
>> * Connection #0 to host iodine-test.appspot.com left intact
>>
>> time_namelookup:  0.004
>>
>>time_connect:  0.011
>>
>> time_appconnect:  0.000
>>
>>time_pretransfer:  0.011
>>
>>   time_redirect:  0.000
>>
>>  time_starttransfer:  0.023
>>
>> --
>>
>>  time_total:  0.048
>>
>>
>> However, when I deploy this same application to a different project 
>> (iodine-web-prod), caching doesn't occur on *any* of the requests, 
>> regardless of how often I request the same resource. 
>>
>>
>> air:/tmp/plum/deploy-20160727-124350% curl -w 
>> "@/Users/matt/bin/curl-time-format.txt" -o /dev/null -s "
>> http://iodine-web-prod.appspot.com/drug/zoloft; -v
>>
>> *   Trying 216.58.195.241...
>>
>> * Connected to iodine-web-prod.appspot.com (216.58.195.241) port 80 (#0)
>>
>> > GET /drug/zoloft HTTP/1.1
>>
>> > Host: iodine-web-prod.appspot.com
>>
>> > User-Agent: curl/7.43.0
>>
>> > Accept: */*
>>
>> > 
>>
>> < HTTP/1.1 200 OK
>>
>> < Content-Type: text/html; charset=utf-8
>>
>> < Cache-Control: public, max-age=604800
>>
>> < ETag: W/"30a48-XHteNhi+a5i5072zCcVDyg"
>>
>> < Vary: Accept-Encoding
>>
>> < Via: iwer4:25789
>>
>> < X-Cloud-Trace-Context: fd82e108c58b92e3114028fdfcd22105;o=1
>>
>> < Date: Mon, 01 Aug 2016 15:16:46 GMT
>>
>> < Server: Google Frontend
>>
>> < Content-Length: 199240
>>
>> < 
>>
>> { [15256 bytes data]
>>
>> * Connection #0 to host iodine-web-prod.appspot.com left intact
>>
>> time_namelookup:  0.005
>>
>>time_connect:  0.010
>>
>> time_appconnect:  0.000
>>
>>time_pretransfer:  0.010
>>
>>   time_redirect:  0.000
>>
>>  time_starttransfer:  1.503
>>
>> --
>>
>>  time_total:  1.536
>>
>>
>> I've combed through the bits and pieces of unofficial documentation:
>>
>>
>> https://code.google.com/p/googleappengine/issues/detail?id=2258
>>
>>
>> https://web.archive.org/web/20110826081218/http://www.kyle-jensen.com/proxy-caching-on-google-appengine
>>
>>
>> https://groups.google.com/forum/#!topic/google-appengine/6xAV2Q5x8AU/discussion
>>
>>
>> And also reviewed the documentation for Google Cloud CDN assuming that 
>> the policies outlined there are the same as those applied to Appengine. 
>>
>>
>> https://cloud.google.com/cdn/docs/caching
>>
>>
>> However, nothing explains why I would be getting this inconsistent 
>> behavior between projects. Any ideas?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to 

[google-appengine] Re: appengine cloud sql performance issue ,taking too much time to process the request

[Christian F. Howes]

What are you doing with "large data"?  if you are loading large amounts of 
data into ram, processing it and then writing it back to the database it 
will be slower then smaller transactions.  There is a maximum read/write 
throughput and a max CPU speed on your DB and instances.

On Wednesday, August 3, 2016 at 9:23:52 PM UTC-7, ANOOP M.S wrote:
>
> No I haven't used Stackdriver , i will use now and update you. In my case 
> request processing works perfectly with small data, it has a problem when 
> its working with large data and manipulating it. any limitation for app 
> engine in handling large amount of data?
>
> On Thursday, August 4, 2016 at 2:11:03 AM UTC+5:30, Nicholas (Google Cloud 
> Support) wrote:
>>
>> Thanks for providing a little more information.  3 to 4 minutes is indeed 
>> strange but I cannot reproduce this latency.  For testing, I created 
>> 100,000 rows of text columns. Then sent over 100 requests to an App Engine 
>> instance that retrieves a single row (always the same one) and updates it. 
>>  I've had no issues getting these rows updated in under 1 or 2 seconds per 
>> request albeit with some contention issues since always reading/writing to 
>> the same row.
>>
>> To reiterate, I would need a lot more context to help your identify the 
>> source of the bottleneck.  Have you tried using Stackdriver Trace to 
>> identify what is taking the bulk of time to respond to a request?  Is it 
>> when processing the request, connecting to the DB, reading the row, writing 
>> to the row, closing the connection, compiling the response, any of the 
>> above?
>>
>> On Wednesday, July 27, 2016 at 4:39:29 AM UTC-4, ANOOP M.S wrote:
>>>
>>>
>>> 0down votefavorite 
>>> 
>>>
>>> on my django project i am using app-engine with cloud sql, the problem i 
>>> am facing a significant performance issue , app-engine is taking too much 
>>> time to process the request like 3,4 minutes, when i looked at the trace 
>>> its showing a latency below 1.5 seconds which was expected. my app-engine 
>>> is of F1 instance class Min Idle Instances, Max Idle Instances and Max 
>>> Concurrent Requests as auto, and cloud sql is a High memory machines with 
>>> 2CPU 13GB memory.
>>>
>>> and its happening even if i am the only user in the project, i don't 
>>> know where i am going wrong, how can i improve the perfomance?
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ec782708-1417-4fee-9cd4-986aec1d9e86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Stack driver logs not working

[Christian F. Howes]

bummer!  i know the next request is going to be to capture a HAR log of 
the session trying to load the page.  you can submit a ticket in the 
public issue tracker with a special tag that makes it readable by only 
you and google folks (so your private info in the HAR log is not 
exposed).  the logs team has been working hard and been pretty 
responsive to things lately, so i would suggest giving that a try.


cfh

On 8/1/16 18:27, Daniel wrote:

Thanks for answering.  I checked and both my project and my gmail account
are correct.  Other parts of the cloud platform pages work fine, I can see
my appengine dashboard and datastore.  I've often had issues with it
switching accounts on me as well, but this appears to be something else as
far as I can tell

D


On Monday, August 1, 2016 at 3:23:35 PM UTC-7, Christian F. Howes wrote:


quintuple check that you have the right project selected in the top right
(blue) bar of the page.  sometimes the auth mechanisms pick the wrong
google account for me and then all chaos breaks loose.

cfh

On Sunday, July 31, 2016 at 3:24:46 PM UTC-7, Daniel wrote:


I haven't inspected my logs for a while since my app has been stable for
months.. but now it appears the logs have been migrated to a new "stack
driver" system.  When I load up logs I simply get

"Failed to load"

Has anyone else seen this ?

Thanks

Daniel







--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1d327f73-5728-aa98-a4dd-1c539730a6d3%40starmakerinteractive.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Stack driver logs not working

[Christian F. Howes]

quintuple check that you have the right project selected in the top right 
(blue) bar of the page.  sometimes the auth mechanisms pick the wrong 
google account for me and then all chaos breaks loose.

cfh

On Sunday, July 31, 2016 at 3:24:46 PM UTC-7, Daniel wrote:
>
> I haven't inspected my logs for a while since my app has been stable for 
> months.. but now it appears the logs have been migrated to a new "stack 
> driver" system.  When I load up logs I simply get 
>
> "Failed to load"
>
> Has anyone else seen this ? 
>
> Thanks 
>
> Daniel
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7600d4ef-d0ea-431e-aa1d-a7c72dfdf2e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unable to create directory wp-content/uploads/2016/07

[Christian F. Howes]

you need to update your wordpress to write data to a GCS bucket.  I think 
https://wordpress.org/plugins/google-app-engine/ is the plugin we have used 
for that.

good luck!

On Friday, July 29, 2016 at 1:05:26 PM UTC-7, B Modela wrote:
>
> Unable to create directory wp-content/uploads/2016/07. Is its parent 
> directory writable by the server?
>
> I installed Wordpress with Google App Engine on my windows system but I 
> get the above error each time I try to upload an image or install a 
> plugin/theme. How do I resolve this. Thanks in advance.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2c042f17-53f1-4eda-b740-8ab9841963f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Task size limit on Flexible env

[Christian F. Howes]

correct, the restrictions of the environment are lifted, but the 
restrictions of the associated services are not.  So the task queue service 
still has a payload size limit, as that is an off-instance service.  
(similarly the max size of an entity in NDB is still the same).

i can't find the docs right now, but i think the payload size is around 
1MB, but might be completely wrong.  the new documentation structure hides 
a lot of these details that were easy to find in the older docs.

On Friday, July 29, 2016 at 10:49:24 PM UTC-7, Deepak Singh wrote:
>
>
> As far as i know all of the restrictions of standard env have been removed 
> on flexible env, but we still get exception on task queue on flexible env
>
> textPayload: "java.lang.IllegalArgumentException: Task size too large" 
>
>  
> What is this limit ?
>
> -- 
> Tech
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b003c9b0-4772-4c80-89c7-7600f01cf009%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: GAE Latency & Instance issues

[Christian F. Howes]

looks like the pending MS logs mystery was solved: 
https://groups.google.com/forum/#!topic/google-appengine/8mHxjsSCOYc  so if 
you don't see that in your logs you can rule that out as a problem.

On Friday, July 29, 2016 at 10:04:47 AM UTC-7, Christian F. Howes wrote:
>
> A helpful stat would be the "pending latency" (the amount of time that 
> the request waited for an available instance to run on).  This was part 
> of the logs in the old log viewer and is missing is the new log viewer. 
> i believe someone has filed an issue requesting that it be re-added. 
>
> if any of your requests are cacheable, setting proper cache headers will 
> trigger google's edge cache and dramatically reduce server side latency 
> as well. 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f511d2e9-b4b3-4f15-a089-0bbb30bd72dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: GAE Latency & Instance issues

[Christian F. Howes]

A helpful stat would be the "pending latency" (the amount of time that 
the request waited for an available instance to run on).  This was part 
of the logs in the old log viewer and is missing is the new log viewer. 
i believe someone has filed an issue requesting that it be re-added.


if any of your requests are cacheable, setting proper cache headers will 
trigger google's edge cache and dramatically reduce server side latency 
as well.


On 7/29/16 09:15, Deepak Singh wrote:

We have our application
Java, flexible env - autoscaling

Almost all of our logs show the following statistics

ms=346 cpu_ms=0 cpm_usd=1.32769e-7 loading_request=0 instance=-
app_engine_release=1.9.42 trace_id=-

Our users face front end latency. Is it any server issue Or any corrective
measures can be taked.




On Wed, Jul 27, 2016 at 2:12 PM, ANOOP M.S  wrote:


but my latency is only below 1.5 seconds when i looked at the log that's
ok for me, i have an issue with the time taking for the prepossessing or is
it the same thing, i will start a new thread with issue anyway

On Wednesday, July 27, 2016 at 9:35:18 AM UTC+5:30, Trevor wrote:


I simply followed the advice kindly offered in this thread and
experimented with lowering the max concurrent requests. Our best settings
ended up being 2 max concurrent requests with 2 max idle instances.

I think an important part is that before this tweaking, we separated our
front-end and task modules (recently renamed services) such that their
instances could be completely independent.

By taking those two steps, our front-end average latency fell from an
average of 600ms to 180ms, and our daily instance costs went from $100 to
$30. So performance improved while cutting costs by >60%. We're pretty
happy with the results.

--

You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/c8b7af68-6f26-40fe-95c4-cea0b96e5562%40googlegroups.com

.

For more options, visit https://groups.google.com/d/optout.







--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1b15be55-3dfb-25ea-3c5f-61c1b8389b4a%40starmakerinteractive.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: show failed to load when opening task queues in gae webconsole

[Christian F. Howes]

we see this problem intermittently as well.  usually a refresh or two it 
and resolves, but it sounds like you are more stuck then that.

On Friday, July 15, 2016 at 9:38:09 PM UTC-7, Mobilewalla Inc. wrote:
>
> Hi
>
> I cannot see my task queues on gae web console.
> I is showing failed to load. Same problem on chrome incognito and firefox 
> private browsing.
>
> thanks
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a37a0435-32a0-4f9e-b2b6-9ae1109865ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Usability of new logs viewer

[Christian F. Howes]

Thanks Nick.

Most of them have been filed over there and been ignored for months.  I 
have also been told to not post information from my support tickets 
publicly, so I will leave it to the support team to convert my internal 
tickets to public items.


thanks,

Christian

On 7/8/16 12:51, 'Nick (Cloud Platform Support)' via Google App Engine 
wrote:

Hey Christian,

If you can turn any of those into Feature Requests or Bug Reports in the Public
Issue Tracker for the Cloud Platform
<http://code.google.com/p/google-cloud-platform/issues/list>, we'd be happy
to handle them!

Cheers,

Nick
Cloud Platform Community Support

On Thursday, July 7, 2016 at 3:13:40 PM UTC-4, Christian F. Howes wrote:


I too am having problems with the new log viewer, and have a p1 support
ticket open with Google.  I have the same problems you list plus:

  - too many errors trying to load the logs pages
  - too slow to load the page
  - truncated user-agent string (this is a blocker for our use of the logs
because the user-agent string tells us which client is connecting!)
  - less information in the collapsed view of the logs compared to the old
console which tremendously slows down our scanning of the logs for issues.

i am disappointed that Google turned down the old viewer before full
feature parity was achieved.

christian

On Thursday, July 7, 2016 at 6:01:55 AM UTC-7, Mark Cummins wrote:


The old App Engine console is gone (sadness). The new logs viewer has
improved a lot, but it's still frustrating compared to the old viewer.

Here are a few things which really bug me, I wonder if anyone has come up
with work-arounds or solutions:

1) Collapse the metadata block [part in curly braces]
In the expanded view, every log shows the expanded metadata block in
curly braces first. This consumes massive chunks of my screen real estate,
while containing information that is mostly irrelevant most of the time.
I'd like this block to be collapsed, so I can just see the
info/warning/error messages that contain the useful information most of the
time. That would allow me to much more quickly browse the logs and see
useful information.

2) Disable auto-update on scroll
Generally I want to work with a block of logs for a while when diagnosing
a problem. I find the auto-refresh on scroll unhelpful. As I scroll around
new logs get loaded and it's easy to lose my place. The old paged view was
much more practical. Is there a way to disable this?

Hopefully some people have work arounds, I really feel like I have no
idea what's going on in my app any more now that we're forced to use the
new viewer. Small UI differences have a big impact on usability. Colour
scheme is also bad, but I have no hope of Google improving that.







--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/57800708.7070704%40starmakerinteractive.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Usability of new logs viewer

[Christian F. Howes]

I too am having problems with the new log viewer, and have a p1 support 
ticket open with Google.  I have the same problems you list plus:

 - too many errors trying to load the logs pages
 - too slow to load the page
 - truncated user-agent string (this is a blocker for our use of the logs 
because the user-agent string tells us which client is connecting!)
 - less information in the collapsed view of the logs compared to the old 
console which tremendously slows down our scanning of the logs for issues.

i am disappointed that Google turned down the old viewer before full 
feature parity was achieved.

christian

On Thursday, July 7, 2016 at 6:01:55 AM UTC-7, Mark Cummins wrote:
>
> The old App Engine console is gone (sadness). The new logs viewer has 
> improved a lot, but it's still frustrating compared to the old viewer.
>
> Here are a few things which really bug me, I wonder if anyone has come up 
> with work-arounds or solutions:
>
> 1) Collapse the metadata block [part in curly braces]
> In the expanded view, every log shows the expanded metadata block in curly 
> braces first. This consumes massive chunks of my screen real estate, while 
> containing information that is mostly irrelevant most of the time. I'd like 
> this block to be collapsed, so I can just see the info/warning/error 
> messages that contain the useful information most of the time. That would 
> allow me to much more quickly browse the logs and see useful information.
>
> 2) Disable auto-update on scroll
> Generally I want to work with a block of logs for a while when diagnosing 
> a problem. I find the auto-refresh on scroll unhelpful. As I scroll around 
> new logs get loaded and it's easy to lose my place. The old paged view was 
> much more practical. Is there a way to disable this?
>
> Hopefully some people have work arounds, I really feel like I have no idea 
> what's going on in my app any more now that we're forced to use the new 
> viewer. Small UI differences have a big impact on usability. Colour scheme 
> is also bad, but I have no hope of Google improving that.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/45f7c3b3-98a6-482b-9215-fba81473d651%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: GAE Latency & Instance issues

[Christian F. Howes]

2 thoughts:

 - remember that when servicing multiple simultaneous requests the CPU is 
switching between them.  I bet the pauses are (in part) due to waiting for 
a turn on the CPU - your request got "paused" while the memcache call was 
made, and then had to wait for CPU once the memcache response was ready.
 - based on the description of what the pages are doing, have you tried 
using "Edge Cache"?  it's very under-documented, but when the state of a 
page is the same for many users it's a big $$$ saver.  see 
https://code.google.com/p/googleappengine/issues/detail?id=2258 and 
https://cloud.google.com/appengine/docs/python/how-requests-are-handled#cache-control_expires_and_vary

good luck!

cfh

On Tuesday, July 5, 2016 at 11:24:46 AM UTC-7, Nick (Cloud Platform 
Support) wrote:
>
> Hey Folks,
>
> As for the amount of concurrent requests an instance can handle, it 
> depends on the CPU usage on the instance, and the number of concurrent 
> requests the instance can handle is dependent on that, and the distribution 
> of requests to instances is also dependent on statistical trends in 
> latency. It's possible to see variable concurrent request performance 
> dependent on how requests use up the resources for the given instance 
> class 
> 
>  
> and the latency statistics of requests on an instance.
>
> I have one small recommendation relating to the mysterious gaps of time in 
> requests. Using System.currentTimeMillis() 
> 
>  
> calls (this is for java, but other runtimes have equivalent system calls) 
> to surround calls to complex libraries, or any calls which require network 
> activity, and you could be able to determine what exactly is taking up that 
> time. It might be something optimize-able, or it might be a network issue. 
> Depending on the nature of the network call itself, it could also be 
> optimize-able.
>
> Regards,
>
> Nick
> Cloud Platform Community Support
>
> On Friday, July 1, 2016 at 3:28:51 AM UTC-4, Thomas Taschauer wrote:
>>
>> One thing I noticed is that the first request(s?) served by a fresh 
>> instance will always be really slow. Not that they stay in the request 
>> queue for a longer time (which is expected behaviour of course), but they 
>> have long "pauses" in the middle of the request as you mentioned before, 
>> usually up to 5 seconds in my case.
>>
>> What I'm going to test next is upgrading to F2 - hoping for smaller 
>> pauses due to a faster CPU - and reverting other scaling-options to default 
>> (used max_concurrent_requests and max_idle_instances before) hoping for the 
>> AppEngine scaler to figure it out himself. :)
>>
>> On Thursday, June 30, 2016 at 1:13:42 PM UTC+2, troberti wrote:
>>>
>>> Great to hear that it helps. Actually, if you are using F4s, I might try 
>>> a slightly higher max_concurrent_requests , say 4. Again, test and compare 
>>> to be sure.
>>>
>>> Finally, to reduce costs, I would recommend to set max_idle_instances to 
>>> 1. Keep min_idle_instances to what you need for your application. For us 
>>> this reduces cost significantly without any apparent drawbacks.
>>>
>>> On Thursday, June 30, 2016 at 11:44:34 AM UTC+2, Trevor wrote:

 Well, I have to say thank you very, very much. Thanks to your advice we 
 have our lowest latency in 3 years! Sub 300ms average.  As expected 
 though, 
 we are now sitting on 21 billed f4 instances, which will potentially cost 
 us in the order of 3x our current ($30-40 -> $100+), but we will tweak 
 that 
 from tomorrow onwards. Peak hour is about to hit so we are going to see if 
 the system can keep sub-300ms at the current "automatic" setting for 
 scaling. But yes, once again, thank you for solving in 5 minutes what I 
 have been working on doing for 2 weeks (my tears are from joy and sadness 
 all at once)


 


 


 On Thursday, June 30, 2016 at 6:03:23 PM UTC+9, troberti wrote:
>
> Right, you should definitely test and see what the results are. My 
> first inclination was also to increase max_concurrent_requests, but 
> because 
> then all those requests have increased latency, the actual QPS per 
> instance 
> decreased! Lowering max_concurrent_requests decreased request latency, so 
> each instance could process more requests/second.
>
> We use F1 instances, because we do not need the additional memory, and 
> our requests perform mostly RPCs. In our testing, 

[google-appengine] Re: ImportError: No module named google.appengine.api

[Christian F. Howes]

i am not familiar with the tools you mention, are the GAE tools?  are you 
running them in the GAE environment?  if you are trying to invoke tools 
from the command line, please be sure that your python path includes the 
google tooling, you might want to setup a virtualenv for this.  when i 
setup my virtualenv i did:

GAESDK=[PATH_TO_YOUR_GAE_SDK]
add2virtualenv $GAESDK/lib/webapp2-2.5.2/
add2virtualenv $GAESDK/lib/webob-1.2.3/
add2virtualenv $GAESDK/lib/yaml-3.10/
add2virtualenv $GAESDK/lib/python-gflags/
add2virtualenv $GAESDK


plus a few others that were specific to my project.

On Tuesday, June 14, 2016 at 8:24:30 PM UTC-7, EJ Kowal wrote:
>
> I am having some issues with running python manage.py collectstatic. I get 
> this error now:
>
> Traceback (most recent call last):
>   File "manage.py", line 12, in 
> execute_from_command_line(sys.argv)
>   File "lib/django/core/management/__init__.py", line 385, in 
> execute_from_command_line
> utility.execute()
>   File "lib/django/core/management/__init__.py", line 354, in execute
> django.setup()
>   File "lib/django/__init__.py", line 21, in setup
> apps.populate(settings.INSTALLED_APPS)
>   File "lib/django/apps/registry.py", line 115, in populate
> app_config.ready()
>   File "lib/django/contrib/admin/apps.py", line 22, in ready
> self.module.autodiscover()
>   File "lib/django/contrib/admin/__init__.py", line 23, in autodiscover
> autodiscover_modules('admin', register_to=site)
>   File "lib/django/utils/module_loading.py", line 74, in 
> autodiscover_modules
> import_module('%s.%s' % (app_config.name, module_to_search))
>   File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in 
> import_module
> __import__(name)
>   File "/home/edk/workspace/completerecipes/core/admin.py", line 13, in 
> 
> from core.forms import RecipeCategoryForm
>   File "/home/edk/workspace/completerecipes/core/forms.py", line 9, in 
> 
> from google.appengine.api import memcache
> ImportError: No module named google.appengine.api
>
>
> Everything I have tried so far has been to no avail, I am not sure exactly 
> what I need to do to be able to run collectstatic.
>
> Thanks for reading!
>
> Eddie
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2a169eda-17d4-448f-9ad2-50f49b18a801%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: project with python and node services: inconsistent data

[Christian F. Howes]

Does your node service use NDB or DB?  if it is using NDB then NDB takes 
care of flushing the cache for you when you update an object, but you have 
to `get_by_key` in order to get the latest copy.

On Wednesday, June 8, 2016 at 1:33:15 AM UTC-7, Faried Nawaz wrote:
>
> Hello,
>
> I have a Python application deployed as my App Engine project's default 
> service.  I also have a node service deployed in the same project for 
> long-running tasks (uploads of large files to GCS).  After a file is 
> uploaded, the node code updates an existing Datastore object with the path 
> to the file on GCS.
>
> I've noticed that if I fetch the object from the Python service after the 
> update, I don't always get the latest data.  Other than by sprinkling 
> use_cache=False, 
> use_memcache=False in a bunch of places on the Python side (and taking a 
> performance hit), how can I work around this problem?  Is there any way for 
> the node service to flush or update the object in memcache?  I use ndb on 
> the Python side.
>
>
> Faried.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0a71de1c-b14d-4d5c-a01b-2fb6cfd69ca9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: cgloud app preview deploy process takes ~8 minutes, is this normal?

[Christian F. Howes]

based on my experience with managed vms (and now flexible runtimes) this is 
normal.  my machines are python based with the app engine compatibility 
layer.

the time i think is spent making a new docker image.  i too would like for 
it to be faster.

cfh

On Tuesday, June 7, 2016 at 6:17:55 AM UTC-7, Ward Bekker wrote:
>
> Hello,
>
> Trying out the new flexible app engine runtime. In this case a custom Ruby 
> on Rails runtime based on the google provided ruby runtime.
>
> When firing of `cgloud app preview deploy` the whole process takes ~8 
> minutes, most of which is "updating service". Is this normal? And more 
> importantly, how can I speed it up?
>
> Regards,
>
> Ward
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9d5cdb1f-9791-4e1e-b8d3-da5628e881ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Fire and forget URL

[Christian F. Howes]

note that if you use the urlfetch async (which was going to be my 
suggestion as well) that you do need to wait at the end of your request 
handler for the future or the request will be killed if it hasn't completed 
yet.

On Tuesday, May 24, 2016 at 12:08:21 PM UTC-7, Chad Vincent wrote:
>
> There is an Async method on the URLFetchService (in Java, at least) that 
> you can call and just never process the Future.
>
> URLFetchService.fetchAsync(HTTPRequest)
>
> On Tuesday, May 24, 2016 at 11:29:17 AM UTC-5, Ashley Finney wrote:
>>
>> In GAE I want to fire a Post message at a URL but I do not want to wait 
>> for the response, the call should be as quick and 
>> cheap (cpu/memory/cost) as possible.  All I'm doing is using this to send a 
>> message to another server.  I don't mind if I lose messages.
>> Instead of using "appengine/urlfetch" is there another method?
>>
>> Many thanks.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9b8d139a-7ba1-4a7f-a58b-f7c3db6a3ba3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Using Pull Task Queue REST API outside App Engine?

[Christian F. Howes]

have you used appcfg.py update_queues?

https://cloud.google.com/appengine/docs/python/tools/appcfg-arguments#update_queues

On 5/16/16 11:59, Cristian Mastrantono wrote:

After more research... my conclusion is that the queue must be created with
a GAE app... and then you can use it from CE. Because even if I define the
queue in my queue.yaml (CE) it is not created. Never.

Maybe someone can confirm this.



On Monday, May 16, 2016 at 3:40:47 PM UTC-3, Christian F. Howes wrote:


Hi,

you ask: "*now I'm wondering if the queue must be created first before
start using it"* I am pretty sure that even on GAE you must update
queue.yaml and deploy the new queue before GAE can use it, so I'd assume
that is the same for the REST API.  I don't think that you can create
queues on the fly, but you can use parameters on the tasks, or different
URLs on the tasks to handle them differently.

good luck,

cfh

On Friday, May 13, 2016 at 6:37:05 AM UTC-7, Cristian Mastrantono wrote:


I'm having trouble dealing with the Pull Task Queue REST API. Whenever I
try it says "403 - you are not allowed to make this api call". I'm trying
this in my computer, which is obviously out of the App and Compute Engine.


I have my Service account credential, my queue.xml in WEB-INF, and *now
I'm wondering if the queue must be created first before start using it* ...
is that necessary?


This is my code... Am I missing something?


JsonFactory JSON_FACTORY = JacksonFactory.getDefaultInstance();
HttpTransport httpTransport = GoogleNetHttpTransport.newTrustedTransport();

List scopes = new ArrayList<>();
scopes.add(TaskqueueScopes.TASKQUEUE);
scopes.add(TaskqueueScopes.TASKQUEUE_CONSUMER);

ClassLoader classloader = Thread.currentThread().getContextClassLoader();
InputStream is = classloader.getResourceAsStream("credential-12356.json");

GoogleCredential credential = 
GoogleCredential.fromStream(is).createScoped(scopes);

Taskqueue taskQueue = new Taskqueue.Builder(httpTransport, JSON_FACTORY, 
credential).setApplicationName(APPLICATION_NAME).build();

Taskqueue.Taskqueues.Get request = taskQueue.taskqueues().get(projectId, 
taskQueueName);
request.setGetStats(true);

//Get the queue!
TaskQueue queue = request.execute();








--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/573A2C3D.9060004%40starmakerinteractive.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How to avoid ,"Google Cloud Platform & APIs billing account suspension" ?

[Christian F. Howes]

Hi Zia,

Maybe you need to use different email addresses to create the accounts?

I found recently that i could download a CSV of my detailed billing data at 
the end of the month (I am on invoiced monthly billing), and from there i 
can filter out costs by project.  see 
https://console.developers.google.com/billing//invoices  and/or 
https://console.developers.google.com/billing//export

hope that helps!

cfh

On Saturday, May 14, 2016 at 8:44:04 PM UTC-7, Zia M wrote:
>
> Hi,
>
> My scenario requires me to create multiple billing account, I want 
> separate billing account to be attached with each project so I have exact 
> cost of each project running for this purpose I want to create multiple 
> billing account.However, as soon as I create a billing account, I receive 
> automatic email with subject,"Urgent: your Google Cloud Platform & APIs 
> billing account XX-XX-XX has been suspended" and the billing 
> account is closed.
>
> Anyone here care to suggest, what should I do to avoid this ?
>
> I am facing this problem even if I upload and verify all my documents for 
> the first billing account, the first account is verified and reinstated, 
> however, again when I create 2nd billing account with same details, I face 
> suspension again.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ed96177b-c77f-47af-877a-33f260b28b8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Problem with russian file names and names with blank spaces on google cloud storage

[Christian F. Howes]

What is the response from the REST API when you attempt to delete?

have you tried the gcloud command line tool?  does it fail in the same way?

my only thought is encoding or escaping the special characters is the 
problem.  I am curious about the answer!

good luck,

cfh

On Friday, May 13, 2016 at 5:36:31 AM UTC-7, Никита Гуртовой wrote:
>
>
> Hello there!
> I have some sad issue with rusian file names and names with blank spaces 
> on google cloud storage. Sorry for posting this message here, but GCS 
> haven't their own group.
>
> My problem is:
>
> When i store files in GCS with names, that contain blank spaces or russian 
> character in their name, I can't delete them, using REST API.
>
> My batch delete method is:
>
> def gcs_batch_delete(gcs_file_names):
>  logging.debug('Deleting ' + str(len(gcs_file_names)) + ' files.')
>
>  boundary = '===7330845974216740156=='
>  headers = {'Content-Type': 'multipart/mixed; boundary="' + boundary + '"'}
>  data = '--' + boundary + '\n'
>  template = """Content-Type: application/http
>
> DELETE /storage/v1/b/%s/o/""" % os.environ['GCS_BUCKET_NAME']
>  bodies = [template + urllib.quote_plus(filename) + '\n' for filename in 
> gcs_file_names]
>  data += ('\n--' + boundary + '\n').join(bodies)
>  data += '\n--' + boundary + '\n'
>
>  logging.debug('Request:\n' + data)
>
>  url = 'https://www.googleapis.com/batch'
>  result = urlfetch.fetch(url=url, payload=data, method=urlfetch.POST, 
> headers=headers)
>
>  logging.debug('urlfetch result: ' + str(result.content))
>
> One moment here:  I can't store files in GCS with names, that differ from 
> original name.
>
>
> So, i need to make a nice looking request to GCS to perform my batch delete. 
>
> In this request file name must be exactly as it written to GCS.
> Already asking this on overflow, but nothing helped. 
>
>
> Hope, guys, u can help me to solve my problem :3
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/42106ae8-9942-41db-bbc2-599797567eb1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Using Pull Task Queue REST API outside App Engine?

[Christian F. Howes]

Hi,

you ask: "*now I'm wondering if the queue must be created first before 
start using it"* I am pretty sure that even on GAE you must update 
queue.yaml and deploy the new queue before GAE can use it, so I'd assume 
that is the same for the REST API.  I don't think that you can create 
queues on the fly, but you can use parameters on the tasks, or different 
URLs on the tasks to handle them differently.

good luck,

cfh

On Friday, May 13, 2016 at 6:37:05 AM UTC-7, Cristian Mastrantono wrote:
>
> I'm having trouble dealing with the Pull Task Queue REST API. Whenever I 
> try it says "403 - you are not allowed to make this api call". I'm trying 
> this in my computer, which is obviously out of the App and Compute Engine.
>
>
> I have my Service account credential, my queue.xml in WEB-INF, and *now 
> I'm wondering if the queue must be created first before start using it* ... 
> is that necessary?
>
>
> This is my code... Am I missing something?
>
>
> JsonFactory JSON_FACTORY = JacksonFactory.getDefaultInstance();
> HttpTransport httpTransport = GoogleNetHttpTransport.newTrustedTransport();
>
> List scopes = new ArrayList<>();
> scopes.add(TaskqueueScopes.TASKQUEUE);
> scopes.add(TaskqueueScopes.TASKQUEUE_CONSUMER);
>
> ClassLoader classloader = Thread.currentThread().getContextClassLoader();
> InputStream is = classloader.getResourceAsStream("credential-12356.json");
>
> GoogleCredential credential = 
> GoogleCredential.fromStream(is).createScoped(scopes);
>
> Taskqueue taskQueue = new Taskqueue.Builder(httpTransport, JSON_FACTORY, 
> credential).setApplicationName(APPLICATION_NAME).build();
>
> Taskqueue.Taskqueues.Get request = taskQueue.taskqueues().get(projectId, 
> taskQueueName);
> request.setGetStats(true);
>
> //Get the queue!
> TaskQueue queue = request.execute();
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3b8cabe2-48d7-4b9b-91d7-79d218293153%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Unwelcome change: Paginating the task queue list

[Christian F. Howes]

great thanks!  I never know what the release cycles are for the console.

Christian

On 4/29/16 16:09, 'Kim Lewandowski' via Google App Engine wrote:

Hi Christian,

I can say with pretty high confidence this fix should be live by next
Thursday (May 5, 2016).

On Thursday, April 28, 2016 at 9:15:42 AM UTC-7, Jeff Schnitzer wrote:


Hi Google…

Yesterday I noticed that the “task queue” viewer in the cloud console was
changed to paginate the results every 10 entries. I can no longer see the
state of all my queues at a glance. Constantly clicking through four pages
is irksome, especially when there is a vast sea of blank space on my nice
tall monitor.

My app performs a lot of orchestration based on task queues; checking to
see if any of the jobs are backed up is part of our standard measurement of
the general health of the system. This just got a lot more painful.

If you have to paginate, please make the list hundreds long. Not 10. I
heard my entire team scream in agony, one at a time, as they noticed the
change :-(

Thanks,
Jeff








--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/572781B6.1010603%40starmakerinteractive.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unwelcome change: Paginating the task queue list

[Christian F. Howes]

Kim,

what's the release cycle for the console?  is the next release or 2 
measured in days, weeks, or months?  this change really slows down our 
workflow and increases our costs to manage the platform.  it's quite sad 
that we keep eroding one of the biggest features of GAE - simple 
management, by making changes like this.

Thanks,

Christian


On Thursday, April 28, 2016 at 1:37:14 PM UTC-7, Kim Lewandowski wrote:
>
> Hi Everyone,
>
> Thanks for the feedback. I've submitted a bug to get this increased to 100 
> queues/tasks per page. The fix should go out in the next release or 2.
>
> Also, I'm gathering requirements on making the Task Queues and Cron UI 
> even better. If you have more feedback to share, please email it to me! 
> lil...@google.com 
>
> -Kim Lewandowski
> App Engine, Product Manager
>
> On Thursday, April 28, 2016 at 9:15:42 AM UTC-7, Jeff Schnitzer wrote:
>>
>> Hi Google…
>>
>> Yesterday I noticed that the “task queue” viewer in the cloud console was 
>> changed to paginate the results every 10 entries. I can no longer see the 
>> state of all my queues at a glance. Constantly clicking through four pages 
>> is irksome, especially when there is a vast sea of blank space on my nice 
>> tall monitor.
>>
>> My app performs a lot of orchestration based on task queues; checking to 
>> see if any of the jobs are backed up is part of our standard measurement of 
>> the general health of the system. This just got a lot more painful.
>>
>> If you have to paginate, please make the list hundreds long. Not 10. I 
>> heard my entire team scream in agony, one at a time, as they noticed the 
>> change :-(
>>
>> Thanks,
>> Jeff
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cd5ff1b9-def0-4955-80fa-68e27c672f96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Datastore Admin stopped working

[Christian F. Howes]

Adam,

since this is a required version for administering our applications, can 
Google put in safeties to prevent it from being deleted?  It's pretty scary 
that it can accidently be deleted and not be re-created.

thanks,

christian 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/957d8068-afbc-4952-af97-d494f7239700%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: image.ServingURL very slow (~200ms)

[Christian F. Howes]

i haven't measured the time it takes for the transformation recently, but 
note that the serving URL does not change, so i only generate it when a new 
blob is uploaded and store the URL on the object in my datastore so that it 
takes 0 time to generate in the future.

On Saturday, April 23, 2016 at 5:35:18 AM UTC-7, David de Kloet wrote:
>
> Hello,
>
> I just noticed that turning a blob key into an image serving URL is very 
> slow, often over 200ms.
> Is this expected or am I doing something wrong?
> I assumed that turning a blob key into a serving URL would be a simple 
> string transformation, but even if it needs to make a request to another 
> service, 200ms seems very slow.
> If it makes any difference, I'm using Go, and I just noticed that the 
> "appengine" libraries have been deprecated by "google.golang.org/appengine", 
> but I haven't updated yet.
>
> Thanks,
> David
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4bb00a30-3b0b-4555-8c98-20cc6a299ca7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Does Datastore (or its backups) include multiple versions of an entity?

[Christian F. Howes]

it sounds like you have some write transactions in P1 that never actually 
committed.  those then got backed up and restored to the second project.  
is that possible?  if so then i'm sure you next question is how to detect 
the missed writes.to which i don't have a great answer. :(

cfh

On Monday, April 11, 2016 at 9:54:04 AM UTC-7, Anastasios Hatzis wrote:
>
> Hi, please let me know if this question is better suited for the dedicated 
> Google Cloud Datastore group or some other online resource. However, I use 
> Datastore in combination with GAE Python apps.
>
> This week-end I have migrated one of my production apps and now have 
> received user reports about some stale data in datastore they have 
> discovered, while their corresponding documents in Search API are 
> up-to-date. I'm still looking into the issue, but it seems that the 
> datastore somehow jumped back in time for a few entities of a specific 
> kind, maybe 0.5%, most of them where originally created in the same 
> time-span of a few weeks in late November/early December 2015, though, not 
> all of them in this time-span shown this issue.
>
> Migration steps:
>
>1. Created a new project P2 (in EU)
>2. Deployed the Python code (version V1) to P2 with appcfg.py and 
>waited until all Datastore indexes were shown as "serving"
>3. Datastore backup in project P1 (in US), as of April 9th
>   1. disabled writes for the datastore
>   2. created a backup (all namespaces, all kinds, including a 
>   "_DeferredTaskEntity"), using Cloud Console's "Datastore Admin" page, 
> as 
>   usual stored in my GCS bucket for backups
>4. In project P2, again with "Datastore Admin" page, right after 
>backup in P1 completed:
>   1. disabled writes the almost empty datastore (none of them of the 
>   kind that has shown the issue later)
>   2. imported the same backup information from the backup bucket, and 
>   restored into P2's datastore, again: all kinds, all namespaces
>   3. when the restore tasks were completed, I enabled datastore writes
>5. Deployed the Python code (version V2) to P2 and did run a batch 
>handler that changed a property value of all entities, where each entity's 
>version counter is increased +1, the updated timestamp changes 
>automatically, and the corresponding search doc is updated, too.
>6. For Search API of P2: wiped all documents from all indexes in 
>Search API (just in case); when wipe tasks completed, queried the 
>datastore entities and wrote excerpts of them as search documents
>
> Interestingly, for the effected entities of that kind, the corresponding 
> search doc in Search API has more recent data than the original entity in 
> datastore.
>
> Datastore Entity in P1 and P2:
>
>- version counter: *8*
>- last update on: 2016-*02*-15
>- status: '*executing*'
>
> Search document of this entity in P1 and P2:
> (search doc ID is always the URLsafe encoded NDB key, and I can tell from 
> all other fields/properties, it is the correct search doc)
>
>- version counter: *13*
>- last update on: 2016-*03*-15
>- status: '*completed*'
>
>
> In P1 I had expected, that the entity has the same data than its search 
> doc, but in fact was stale.
>
> In P2, I have expected for both, entity and search doc:
>
>- version counter: *14*
>- last update on: 2016-*04-10*
>- status: '*completed*'
>
> because of the migration script that updated one property for all entities 
> in this kind, and should also have triggered an update of the search doc.
>
> There are two observations:
>
>1. *P1's entity already had stale data*, older than the search doc. 
>This could be explained with an inconsistent / failed write to the 
>datastore, at least in theory. The app uses transactions for 
>reading/writing of this kind. In _post_put_hook(), *if 
>future.check_success() is None*, the search doc is written/updated. I 
>can think of exotic situations where the search doc could be older than 
> its 
>original entity in datastore, but since the datastore write happens in a 
>transaction, and the search export happens only with a successful write 
>operation, I fail to explain how the entity in datastore could prevail the 
>change (or revert to an older version). We talk about 5 different types of 
>changes during one month that have all been lost. There are also no 
>deferred tasks that write potentially old entities back into the datastore.
>2. *P2's entity again shows stale data,* older than the search doc. 
>This is particularly confusing, because the search doc is only written 
> with 
>the data read from datastore. And since the search docs were not copied 
>from P1, the only source was the data freshly restored from the P1 backup. 
>Although, if I look into the P1 datastore, as shown above, the data is 
>already stale. Where did P2's datastore then get the new 

[google-appengine] Re: I'm a Devops Engineer - I must wrestle GAE to the ground - Hints and Tips Please

[Christian F. Howes]

I have not deployed java, but using the technique that Nick mentions below 
to use appcfg on "war folders" makes sense.  I use appcfg for python 
deployments, and my team and i have scripted the crap out of it!  if your 
dev team can deliver you the compiled java code you should be able to get 
scripted deployments running pretty quickly.

cfh

On Monday, April 4, 2016 at 7:18:31 AM UTC-7, Mister Guru wrote:
>
> I'm trying to do some research on GAE - I've inherited the responsibility 
> of maintenance of the infrastructure, and to my delight, (or horror, 
> depending on how you see it), not much documentation existed regarding 
> setup, configuration etc. This means that I have to take the time to learn, 
> document, and script using GAE.
>
> I checked out reddit - https://www.reddit.com/r/gae/ - Which made me very 
> sad, I was hoping for a vibrant community of users.
>
> I'm not a developer, I'm a system admin person - the one thing that is 
> grinding my gears at the moment, is deployments.
>
> I'm a little upset that I can't just go  run it> From what the devs have told me, deployments are integrated into 
> Maven build process ... already I was like ... *huh* - I don't even know 
> what that means. anyway, I digress,
>
> I'd like to know *Is the only way to deploy to GAE via the maven build 
> job*? It would be a 'shame' if that's the case, but as I'm not up to 
> speed with how java apps are suppose to work, best practices and such, I'm 
> not sure if I'm the one looking at it incorrectly. I've also got a few 
> other questions, but I'm testing the water with this first. I could easily 
> run our workloads on Kubernetes or Mesos, so I'm judging GAE purley on the 
> people who use it! (very professional and scientific, I know!)
>
> If there are any other devops guys in here specifically working on 
> deployments and scripting around GAE, I would like to have a word with you 
> - maybe exchange ideas etc
>
> Thanks,
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/00510a89-5cc3-4acd-bd1d-c5412f0fbaa6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Tardy? Porting to new platform version?

[Christian F. Howes]

note that last week google changed console.developers.google.com to 
redirect to https://console.developers.google.com/apis/library which is not 
what i am expecting.  you probably want to verify that 
https://console.cloud.google.com allows you to load your project.

cfh

On Tuesday, March 29, 2016 at 12:21:00 PM UTC-7, Nick (Cloud Platform 
Support) wrote:
>
> Hey Nick,
>
> This sounds like something that could get a quick solution if filed in the 
> Public 
> Issue Tracker . 
> You should capture a HAR recording of the browser interaction 
>  and explain what 
> you're attempting to do. Be sure, when you create the issue, to attach the 
> label "Restrict-View-EditIssue" so that only Google and yourself can view 
> the thread. We should be able to inspect things from our end and determine 
> what's at the bottom of this issue. In the meantime, you could try to visit 
> console.developers.google.com and see if you can see your projects there. 
> That information will likely be important to the issue when you report it.
>
> Best wishes,
>
> Nick
> Cloud Platform Community Support
>
> On Tuesday, March 29, 2016 at 2:35:51 AM UTC-4, Nick Topper wrote:
>>
>> Hi,
>>
>> In the last few months, is there something I should know about porting my 
>> old old old GAE apps to a new version of the platform?
>>
>> My apps are so stable that I rarely log into the GAE admin-console. 
>>  Today I did -- first time in a long time -- and see that most of the 
>> console is disabled, and clicking the link to the new console yields a 
>> message "You do not have sufficient permissions to view this page."
>>
>> I have a vague recollection that Google sent an email several months ago 
>> about apps needing to be ported to a new something-or-other, but cannot 
>> find it.  Is there a pointer to a description of the changes, and what I 
>> need to do?
>>
>> Thanks,
>> NT
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5eaf2039-a46d-412c-9479-31baac152307%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Cron Jon failing with following error

[Christian F. Howes]

yes.  your custom libraries must not be quite right on the GAE path.  i 
recommend setting up a virtualenv for your local machine that does not have 
any system packages that GAE does not have, and that will help you make 
sure your included library paths are correct.

On Monday, March 14, 2016 at 11:31:49 AM UTC-7, Khalid Razzaq wrote:
>
> There is one realted error I'm getting as well
>
> /base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine
> /runtime/wsgi.py:85: ImportWarning: Not importing directory 
> '/base/data/home/apps/s~apps-1149/1.391373453171312456/urlhandlers': 
> missing __init__.py
>
> Can it be because I'm importing some custom libraries?
>
>
> On Monday, March 14, 2016 at 11:28:05 AM UTC-7, Khalid Razzaq wrote:
>>
>>
>> Same code deployed on development system works fine but once deployed to 
>> production fails with following error:
>>
>>
>> Traceback (most recent call last): File 
>> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/runtime/wsgi.py"
>> , line 240, in Handle handler = _config_handle.add_wsgi_middleware(self.
>> _LoadHandler()) File 
>> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/runtime/wsgi.py"
>> , line 299, in _LoadHandler handler, path, err = LoadObject(self._handler
>> ) File 
>> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/runtime/wsgi.py"
>> , line 85, in LoadObject obj = __import__(path[0]) ImportError: No module 
>> named urlhandlers
>>
>> Following is the URL Handler code
>>
>> import tracebackimport datetimefrom google.appengine.api import 
>> taskqueueimport reimport webapp2from utilities.logger import logThis, 
>> AEL_LEVEL_INFO, AEL_LEVEL_CRITICALfrom constants.constants import 
>> GAET_MASTERTASK_NAME, GAEQ_FOR_MASTERTASKimport sys
>> class QueueAMasterTask(webapp2.RequestHandler): 
>> def get(self):
>> try:
>> dt =datetime.datetime.now()
>> logThis(AEL_LEVEL_INFO, 'Master Task added to its Q at[%s]' 
>> %(dt))
>> task_name = GAET_MASTERTASK_NAME + str(datetime.datetime.now())
>> task_name = re.sub('[^a-zA-Z0-9_-]', '_', task_name)
>> taskqueue.add(queue_name=GAEQ_FOR_MASTERTASK,name=task_name)
>> logThis(AEL_LEVEL_INFO, "OK-MASTER TASK ADD")
>> except taskqueue.DuplicateTaskNameError:
>> logThis(AEL_LEVEL_CRITICAL, "EXCEPTION on QueueAMasterTask-" +   
>>   traceback.format_exc())
>> except:
>> logThis(AEL_LEVEL_CRITICAL, "EXP on QueueAMasterTask-" + 
>> traceback.format_exc())
>>
>> app = webapp2.WSGIApplication([('/QueueAMasterTask', QueueAMasterTask)
>>], debug=True)
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a4fd6eae-ecc9-41f7-a0ff-a02b02ebc2e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: memcache problems with objects over ~3.5k on node/appengine

[Christian F. Howes]

do you have any logging from the GAE side of things?  I have ran into 
issues in the past with things not being pickleable by the GAE memcache 
adapter.  perhaps something about your data is not pickleable?


On Friday, March 11, 2016 at 7:50:59 AM UTC-8, John Pettitt wrote:
>
>
>
> I have an app that works fine on my dev machine (osx, local memcached) but 
> when I move it to appengine it fails. I tracked it to memcache not storing 
> objects over about 3.5k.
>
>
> Here is a little test that runs under express. It takes a length value 
> makes a buffers, sends it to memcache and tries to get it back. It works 
> fine locally up to the expected 1MB limit, however on appengine it fails at 
> around length 3600 +/- 200 (it varies, which is really odd). I've tried 
> several different memcache libs, they all fail the same way.
>
>
> What am I missing?
>
>
> //memcache test.
> app.get('/mct/:len',function(req,res)  {
>   var memcachedAddr = process.env.MEMCACHE_PORT_11211_TCP_ADDR || 'localhost';
>   var memcachedPort = process.env.MEMCACHE_PORT_11211_TCP_PORT || '11211';
>   var memcacheServer = memcachedAddr + ":" + memcachedPort;
>   var Memcached = require('memcached');
>   var client = new Memcached(memcacheServer);
>   var len = req.params.len * 1; //lazy cast to int
>   var text = new  Array(len + 1).join( " " );
>
>   try {
> client.set("testkey",text,600,function(err,val) {
> client.get("testkey",function(err,data) {
> if (data && data.length === text.length) {
> res.send("OK at length " + text.length + " " +data.length);
> } else {
> res.send("Failed at " + text.length + " " );
> }
> });
> })
>   } catch(e) {
> res.send("Failed at " + text.length + " " + e.message);
>   }});
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/32da49cb-ea01-4c71-b67a-3b1911f37a16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: New Log Viewer - Unusable

[Christian F. Howes]

Rajesh,

I'd love to know what the link is to the issue you file in the Public Issue 
tracker as i would like to star it!  I have the same problems and still use 
the old log viewer because of them.

thanks,

christian

On Thursday, March 10, 2016 at 4:01:27 PM UTC-8, Nick (Cloud Platform 
Support) wrote:
>
> Hey Rajesh,
>
> Thanks for taking the time to write your feedback. Unfortunately, this 
> isn't the right place to make such a posting. If you have any concrete 
> issues to report or feature requests to propose, feel free to open a thread 
> in the Public Issue Tracker for the Cloud Platform 
> . We monitor 
> it every day and will react quickly to any issue reports or feature 
> requests there.  
>
> Best wishes,
>
> Nick
> Cloud Platform Community Support
>
> On Thursday, March 10, 2016 at 7:24:24 AM UTC-5, Rajesh Gupta wrote:
>>
>> New Log viewer is slow with many issues.
>> It is just not usable for production logs.
>> I was examining the logs that are 10 days old.  
>> I am using the advance filter.  
>> - Don't know if I am scrolling down, wheather the logs are shown older or 
>> newer
>> - When given the date, don't know, the logs are searching older than the 
>> given date or later than
>> the given date.
>> - Too slow, 
>> - Some times does not fetch the logs even after waiting for 1-2 min.
>> - The menu link 'view - show new logs at the top'.  Don't know which 
>> state that it is, and it does not store the state. There should be a 
>> checkmark, saying it is showing the new logs at top or at the bottom.
>>
>> Request appengine team, to fix the log viewer and make it more pleasant 
>> to use.
>>
>>
>> -- 
>> Rajesh
>> *www.VeersoftSolutions.com *
>> *www.AccountingGuru.net *
>> *Accounting/Inventory/Orders on Google Cloud Platform and Mobile*
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/eb398bb2-3da8-4267-9b8c-31441cbb45ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

[Christian F. Howes]

Lorne,

First off the link to customer support is buried inside some menu option 
that does not show up in search.
While never officially supported, the customer support team taught me how 
to link to an individual log record in the old console.  This has really 
helped me both with internal QA and with customer support tickets.
The links to individual datastore records and query results that were 
missing before have been restored.  thanks!

I just noticed that i cannot get directly to the datastore entries viewer - 
i have to search for the datastore item, click into it, wait for it to 
load, and then select entries and wait for it to load.  this was 1 click in 
the old console.  There are many actions that were 1 click and took much 
less time to load that are now buried under multiple clicks with slow load 
times of the intermediate pages.

It looks like the pagination links are missing from the task queue task 
viewer.  I was just trying to diagnose something with my tasks and can't 
look at any tasks beyond the first 100 in the queue. :(

Thanks for all the attention to helping make this a great tool for us!

Christian



On Saturday, March 5, 2016 at 3:40:10 PM UTC-8, Lorne Kligerman wrote:
>
> I appreciate the detailed description here, it helps a lot in reproducing 
> on our side.  
> I'm curious to hear about individual deep links that seem to be missing. 
>  Christian, could you or others elaborate?
>
>
> On Wednesday, March 2, 2016 at 4:59:03 PM UTC-8, Nickolas Daskalou wrote:
>>
>> For me, the new Cloud Console is more aesthetically pleasing, and it is 
>> indeed nice to have all of Google Cloud in one aggregated console.
>>
>> It can, however, get very clunky at times.
>>
>> The new Logs viewer is a perfect example of this. E.g. hitting enter in 
>> the search box works most of the time, but then there are occasions where 
>> nothing happens. Type in an extra search query, or delete an existing 
>> search item, hit Enter, then nothing. No change in the log items list. 
>> Auto refresh on scroll up/down can be good, until it doesn't work. Then it 
>> gets super frustrating. Clicking on the refresh and play buttons, work 
>> well, until they don't. I've also seen the date/time input clobbered, 
>> seemingly randomly.
>>
>> If I'm on the new Logs viewer page for more than a few minutes at a time, 
>> I find myself having to constantly reload the page to get it working again. 
>> A simple refresh will not do, because the browser's current address bar URL 
>> changes as you use the Logs viewer, and it's possible a simple refresh will 
>> result in a similar unresponsive, quirky view you were already on.
>>
>> So instead, when I want to refresh the Logs viewer (which occurs 90% of 
>> the time I have been on the page for more than a few minutes), I need to 
>> manually delete most of the current URL to get back to the base, "starting" 
>> Logs viewer URL for my current project.
>>
>> I sometimes think about Celine Dion's Titanic song, you know the one that 
>> goes "every night in my dreams, I see you, I feel you"? I feel that way 
>> about the " *· · ·* Loading..." mini status popup in the new Logs 
>> viewer. It haunts me, and sometimes it just won't go away.
>>
>> The new Cloud Console feels half-baked. Well, 80% baked. At least the App 
>> Engine parts do. Or rather, the App Engine parts I use. Another example: 
>> "Could not load instances information. [Dismiss link]" in the App Engine -> 
>> Versions page constantly pops up when I'm trying to switch between modules. 
>> Constantly.
>>
>> Also, this guy:
>>
>> [image: Inline images 2]
>>
>> Sometimes he just can't take the hint and leave.
>>
>> However, as the Iron Sheik once said, besides that everything was great.
>>
>> Nick
>>
>>
>> On 3 March 2016 at 11:33, Christian F. Howes <
>> christi...@starmakerinteractive.com> wrote:
>>
>>> Lorne,
>>>
>>> the other things that hinder us in a measurable way are page load times, 
>>> lack of direct links to individual pages, and finding where things are 
>>> (including having some things missing from the search index).
>>>
>>> on a personal opinion level I really miss having all my app engine 
>>> management tools 1 click away with a full listing in the sidebar.  now 
>>> several of them are 2 clicks away.
>>>
>>> thanks for the continued improvements!  things are getting better in the 
>>> new console and it's close to ready for the switch.
>>>
>>> christian
>>>
>>>
>>&

Re: [google-appengine] New Cloud Console

[Christian F. Howes]

Hi Nick,

Can you just review cloud support case 08706899 for which PIT issues are 
not properly updated?  I've listed them out there in the original filing of 
the case and the response from the support team is that several of them are 
fixed.

Thanks,

Christian

On Monday, March 7, 2016 at 11:15:49 AM UTC-8, Nick (Cloud Platform 
Support) wrote:
>
> Hey Chris,
>
> If you could link which issues those are which have been fixed but not 
> updated, we could take a look and determine whether they should be updated 
> with any new relevant information, such as a fix. Feel free to reply to me 
> in this thread.
>
> Best wishes,
>
> Nick
>
> On Thursday, February 25, 2016 at 1:09:43 PM UTC-5, Christian F. Howes 
> wrote:
>>
>> Thanks Lorne. 
>>
>> Will we also be better at triaging and updating the Public Issue 
>> Tracker?  Paid support told me today that several of the issues I filed 
>> last year are supposedly fixed, but the Public Issue Tracker has yet to 
>> be updated. 
>>
>> The lack of information provided, but the hard deadline on the turn-down 
>> notice really concerns me as I don't have confidence that I will be able 
>> to efficiently and effectively manage my app 6 weeks from now. 
>>
>> Thanks, 
>>
>> Christian 
>>
>> On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote: 
>> > Thanks everyone for the feedback.  Overall, we are going to reach 
>> feature 
>> > parity in the Cloud Platform Console before turning down the Admin 
>> Console. 
>> >   The next communication we send will have more details and will 
>> outline any 
>> > gaps that exist and our plans to address them.  To answer the questions 
>> > asked here: 
>> > 
>> > - the dispatch rules will not be visible right away, but we are 
>> actively 
>> > working on a mechanism for you to view all of your App Engine 
>> configuration 
>> > in one place 
>> > - prohibiting code downloads will not show up in the same way, but this 
>> can 
>> > be managed through roles and upcoming IAM functionality 
>> > - as mentioned already, performance is a known issue that is a top 
>> priority 
>> > for the team 
>> > 
>> > Please continue to log issues as Nick mentioned and we will triage 
>> > accordingly. 
>> > 
>> > Cheers, 
>> > Lorne. 
>> > 
>> > On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote: 
>> >> 
>> >> 1+ for speed. Also, is the requests/seconds coming to the new console? 
>> At 
>> >> least for me that's an easier value to discuss. Besides, the new 
>> console's 
>> >> request/minute do not match the request/second metric in the old 
>> console. 
>> >> 
>> >> On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins 
>> wrote: 
>> >>> 
>> >>> +1 for the speed of the new console. The old console is very 
>> noticeably 
>> >>> faster. 
>> >>> 
>> >>> On Thursday, 25 February 2016 01:58:58 UTC, Christian F. Howes wrote: 
>> >>>> 
>> >>>> Hi Lorne, 
>> >>>> 
>> >>>> Is there any chance that you can share the console roadmap with us? 
>> >>>> given that we are getting the turn-down threats again, and the new 
>> console 
>> >>>> is still missing many features it would be helpful to know which 
>> ones are 
>> >>>> known to the team working on the console and which need new tickets. 
>> >>>> 
>> >>>> Is overall speed of the new console going to be addressed?  I lose 
>> >>>> several developer hours a week using the new console waiting for 
>> things to 
>> >>>> load, and as such my team and I tend to use the old console whenever 
>> >>>> possible. 
>> >>>> 
>> >>>> Thanks, 
>> >>>> 
>> >>>> Christian 
>> >>>> 
>> >>>> On Tuesday, February 23, 2016 at 4:43:55 PM UTC-8, Lorne Kligerman 
>> wrote: 
>> >>>>> 
>> >>>>> I'm happy to report that both features are in the works and will 
>> launch 
>> >>>>> shortly, before the old console is turned down. 
>> >>>>> 
>> >>>>> Cheers, 
>> >>>>> Lorne. 
>> >>>>> 
>> >>>>> 
>> >>>>> On Tuesday, F

[google-appengine] Re: App returning 500 for past hours

[Christian F. Howes]

looks fine here: https://status.cloud.google.com/

On Wednesday, March 2, 2016 at 7:30:48 PM UTC-8, Bharath Kumaar wrote:
>
> Hello all, our app "live-adaptivecourse" is returning 500 internal server 
> error almost 6 hours. No request is getting processed. Is app engine 
> elevated?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/58c8b798-47fa-4ec5-aec6-3b7e80dde092%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

[Christian F. Howes]

Lorne,

the other things that hinder us in a measurable way are page load times, 
lack of direct links to individual pages, and finding where things are 
(including having some things missing from the search index).


on a personal opinion level I really miss having all my app engine 
management tools 1 click away with a full listing in the sidebar.  now 
several of them are 2 clicks away.


thanks for the continued improvements!  things are getting better in the 
new console and it's close to ready for the switch.


christian

On 3/2/16 16:02, 'Lorne Kligerman' via Google App Engine wrote:

We are working to improve our attention to the public issue tracker,
something we acknowledge has slipped but it is by no means an indication
that these items are not important to us and our engineering teams.

Besides the items already mentioned here (usage history, migrate traffic,
logs), could you elaborate on what else would limit your ability to manage
your app from the Cloud Console?

On Thursday, February 25, 2016 at 10:09:43 AM UTC-8, Christian F. Howes
wrote:


Thanks Lorne.

Will we also be better at triaging and updating the Public Issue
Tracker?  Paid support told me today that several of the issues I filed
last year are supposedly fixed, but the Public Issue Tracker has yet to
be updated.

The lack of information provided, but the hard deadline on the turn-down
notice really concerns me as I don't have confidence that I will be able
to efficiently and effectively manage my app 6 weeks from now.

Thanks,

Christian

On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote:

Thanks everyone for the feedback.  Overall, we are going to reach

feature

parity in the Cloud Platform Console before turning down the Admin

Console.

   The next communication we send will have more details and will outline

any

gaps that exist and our plans to address them.  To answer the questions
asked here:

- the dispatch rules will not be visible right away, but we are actively
working on a mechanism for you to view all of your App Engine

configuration

in one place
- prohibiting code downloads will not show up in the same way, but this

can

be managed through roles and upcoming IAM functionality
- as mentioned already, performance is a known issue that is a top

priority

for the team

Please continue to log issues as Nick mentioned and we will triage
accordingly.

Cheers,
Lorne.

On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote:


1+ for speed. Also, is the requests/seconds coming to the new console?

At

least for me that's an easier value to discuss. Besides, the new

console's

request/minute do not match the request/second metric in the old

console.


On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins

wrote:


+1 for the speed of the new console. The old console is very

noticeably

faster.

On Thursday, 25 February 2016 01:58:58 UTC, Christian F. Howes wrote:


Hi Lorne,

Is there any chance that you can share the console roadmap with us?
given that we are getting the turn-down threats again, and the new

console

is still missing many features it would be helpful to know which ones

are

known to the team working on the console and which need new tickets.

Is overall speed of the new console going to be addressed?  I lose
several developer hours a week using the new console waiting for

things to

load, and as such my team and I tend to use the old console whenever
possible.

Thanks,

Christian

On Tuesday, February 23, 2016 at 4:43:55 PM UTC-8, Lorne Kligerman

wrote:


I'm happy to report that both features are in the works and will

launch

shortly, before the old console is turned down.

Cheers,
Lorne.


On Tuesday, February 23, 2016 at 3:52:19 PM UTC-8, PK wrote:


We also need the “Billing/Usage History” equivalent functionality,

has

this page been migrated to the new console?

PK
p...@gae123.com




On Feb 23, 2016, at 3:46 PM, johnP <jo...@thinkwave.com> wrote:

Just got email that old appengine console will be shut off in 6

weeks.

   The new cloud console does not have a "migrate traffic" option in

the

Versions screen.  This was my absolute favorite new feature in a

long, long

time.  Will it be available in the new console?

--
You received this message because you are subscribed to the Google
Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it,

send

an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at

https://groups.google.com/group/google-appengine.

To view this discussion on the web visit


https://groups.google.com/d/msgid/google-appengine/540d27f2-1841-4be8-a21b-17aea883dd84%40googlegroups.com

<

https://groups.google.com/d/msgid/google-appengine/540d27f2-1841-4be8-a21b-17aea883dd84%40googlegroups.com?utm_medium=email_source=footer>


.
For more options, visit https://groups.google

[google-appengine] Re: Images served very slowly this week.

[Christian F. Howes]

Any chance that you changed the caching rules in your app.yaml file for 
your static files?  i suspect that can have an effect on load times.

On Tuesday, March 1, 2016 at 9:00:10 PM UTC-8, Jay Kyburz wrote:
>
> Hey all,
>
> It might be my imagination but I think static resources like images are 
> loading very slowly for my app this week.  It doesn't seem like a latency 
> issue so much as a bandwidth issue. Is that completely crazy?
>
> This image for example
>
> https://blight.ironhelmet.com/images/blight_menu_bg.jpg
>
> It's 382K but it can take up to 8 seconds to download. 
>
> I don't think the problem is on my side as I've had users complaining as 
> well.
>
> I'm not sure where to begin look at where my app might have a problem.
>
> The app-id is *blightsrage*
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b1154dfa-7bfc-4a46-adbb-0e1275ad53a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How do I view logs by thread?

[Christian F. Howes]

Nicholas,

What i think the original poster is trying to say is that if I have a long 
running request (thread on a backend instance) that the log messages get 
interleaved in the new logs viewer.  This makes it nearly impossible to 
figure out what the original request was that triggered a certain log.  The 
old log viewer always has the request/thread's complete set of logs as 1 
entry.  If this is what the original poster was trying to say I'd love to 
star that issue in the public issue tracker!

Rohit - it sound like you are noticing some things that i have also 
noticed.  Have you starred the following issues to vote for your support?
https://code.google.com/p/googleappengine/issues/detail?id=6799
https://code.google.com/p/googleappengine/issues/detail?id=11807
https://code.google.com/p/googleappengine/issues/detail?id=12402

Here's to updates to the log viewer before the old one is shut down!

Christian

On Sunday, February 28, 2016 at 3:08:39 AM UTC-8, Rohit Gupta wrote:
>
> I believe I have the same concern, so perhaps I can provide some more 
> details.
>
> Basically, no combination of options seems to produce the same overview 
> that we had *by default* in the old logs.
>
> I'm not talking about some obscure details. I'm talking about *the 
> information the old logs showed by default*!
>
>
>
> Are you guys are trying to cut costs by removing the old logs viewer? I 
> can definitely appreciate that.
>
> But logs are very important, and we shouldn't have to click and poke and 
> prod to find what we're looking for.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/eaad5e4a-98b2-410d-8d3e-46a56a2e6634%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

[Christian F. Howes]

Thanks Lorne.

Will we also be better at triaging and updating the Public Issue 
Tracker?  Paid support told me today that several of the issues I filed 
last year are supposedly fixed, but the Public Issue Tracker has yet to 
be updated.


The lack of information provided, but the hard deadline on the turn-down 
notice really concerns me as I don't have confidence that I will be able 
to efficiently and effectively manage my app 6 weeks from now.


Thanks,

Christian

On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote:

Thanks everyone for the feedback.  Overall, we are going to reach feature
parity in the Cloud Platform Console before turning down the Admin Console.
  The next communication we send will have more details and will outline any
gaps that exist and our plans to address them.  To answer the questions
asked here:

- the dispatch rules will not be visible right away, but we are actively
working on a mechanism for you to view all of your App Engine configuration
in one place
- prohibiting code downloads will not show up in the same way, but this can
be managed through roles and upcoming IAM functionality
- as mentioned already, performance is a known issue that is a top priority
for the team

Please continue to log issues as Nick mentioned and we will triage
accordingly.

Cheers,
Lorne.

On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote:


1+ for speed. Also, is the requests/seconds coming to the new console? At
least for me that's an easier value to discuss. Besides, the new console's
request/minute do not match the request/second metric in the old console.

On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins wrote:


+1 for the speed of the new console. The old console is very noticeably
faster.

On Thursday, 25 February 2016 01:58:58 UTC, Christian F. Howes wrote:


Hi Lorne,

Is there any chance that you can share the console roadmap with us?
given that we are getting the turn-down threats again, and the new console
is still missing many features it would be helpful to know which ones are
known to the team working on the console and which need new tickets.

Is overall speed of the new console going to be addressed?  I lose
several developer hours a week using the new console waiting for things to
load, and as such my team and I tend to use the old console whenever
possible.

Thanks,

Christian

On Tuesday, February 23, 2016 at 4:43:55 PM UTC-8, Lorne Kligerman wrote:


I'm happy to report that both features are in the works and will launch
shortly, before the old console is turned down.

Cheers,
Lorne.


On Tuesday, February 23, 2016 at 3:52:19 PM UTC-8, PK wrote:


We also need the “Billing/Usage History” equivalent functionality, has
this page been migrated to the new console?

PK
p...@gae123.com




On Feb 23, 2016, at 3:46 PM, johnP <jo...@thinkwave.com> wrote:

Just got email that old appengine console will be shut off in 6 weeks.
  The new cloud console does not have a "migrate traffic" option in the
Versions screen.  This was my absolute favorite new feature in a long, long
time.  Will it be available in the new console?

--
You received this message because you are subscribed to the Google
Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/540d27f2-1841-4be8-a21b-17aea883dd84%40googlegroups.com
<https://groups.google.com/d/msgid/google-appengine/540d27f2-1841-4be8-a21b-17aea883dd84%40googlegroups.com?utm_medium=email_source=footer>
.
For more options, visit https://groups.google.com/d/optout.







--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/56CF4349.4020801%40starmakerinteractive.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

[Christian F. Howes]

Hi Lorne,

Is there any chance that you can share the console roadmap with us?  given 
that we are getting the turn-down threats again, and the new console is 
still missing many features it would be helpful to know which ones are 
known to the team working on the console and which need new tickets.

Is overall speed of the new console going to be addressed?  I lose several 
developer hours a week using the new console waiting for things to load, 
and as such my team and I tend to use the old console whenever possible.

Thanks,

Christian

On Tuesday, February 23, 2016 at 4:43:55 PM UTC-8, Lorne Kligerman wrote:
>
> I'm happy to report that both features are in the works and will launch 
> shortly, before the old console is turned down.
>
> Cheers,
> Lorne.
>
>
> On Tuesday, February 23, 2016 at 3:52:19 PM UTC-8, PK wrote:
>>
>> We also need the “Billing/Usage History” equivalent functionality, has 
>> this page been migrated to the new console?
>>
>> PK
>> p...@gae123.com
>>
>>
>>
>>
>> On Feb 23, 2016, at 3:46 PM, johnP  wrote:
>>
>> Just got email that old appengine console will be shut off in 6 weeks. 
>>  The new cloud console does not have a "migrate traffic" option in the 
>> Versions screen.  This was my absolute favorite new feature in a long, long 
>> time.  Will it be available in the new console?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-appengi...@googlegroups.com.
>> To post to this group, send email to google-a...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/540d27f2-1841-4be8-a21b-17aea883dd84%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1e7c959f-224b-458c-96c0-c1ff498034ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Instance stopped automatically?

[Christian F. Howes]

interesting.

i think even a manually scaled instance may be *rebooted* from time to 
time, but the 6 hour downtime seems like something else went wrong.

i've only had problems with manually scaled instances when i wrote code to 
scale instances that was buggy.  are you use some code to scale your 
instances, or just leaving it at a static setting?

cfh

On Friday, February 19, 2016 at 12:19:11 AM UTC-8, Mayank Bhagya wrote:
>
> How is it that one of my manually-scaled backend instances was 
> automatically disappeared last night?
>
> No, my daily quota-reset or billing-reset is yet to happen after an hour 
> from now.
> But the charts show that my instance was stopped at 0400 +0530 and was 
> restarted at 1030 +0530.
>
> I am already sick of the push-to-deploy setup that breaks every other day.
>
> Come on folks. This is business critical things that you're dealing with.
> We don't expect this from Google. 
> We didn't choose you as our cloud provider so that you can break anything 
> whenever you wish to.
>
> Let me know what more detail do you need from my side in order to 
> investigate this.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b54f3b5b-f5a2-4d0a-89ec-656430ca51ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Tracking Down Read Ops Spikes in the new Dashboard

[Christian F. Howes]

i don't know where to find the data you seek in the new admin

but to analyze particular requests have you tried appstats? 
https://cloud.google.com/appengine/docs/python/tools/appstats?hl=en (i use 
python, but i believe this is available for all supported language 
platforms).  note that in my experience appstats adds measurable latency to 
requests so i only use it in test and not in my production apps/modules.

cfh

On Thursday, February 4, 2016 at 6:33:38 AM UTC-8, Joshua Smith wrote:
>
> I just got my January bill for one of my apps, and it was a lot bigger 
> than usual, due to a spike in database read ops. ($11 vs $2, so it’s not 
> like it’s a crisis :) 
>
> On the old dashboard, I used to be able to go to the billing section and 
> see charges by day, which would help me narrow in on what happened to cause 
> the spike (or if there was just a generally higher usage, pointing to some 
> cron that needs optimization or something). 
>
> On the new dashboard, I don’t see daily ops anywhere. Is that still 
> available? If so, how do I find that? 
>
> If you were looking for a lead on what request is causing a lot of read 
> ops, is there a tool in the dashboard you would use to help find that? 
>
> -Joshua 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c6c78136-6047-4970-ae8e-658054f92fad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Planning to use appengine/datastore/cloud storage. Have few questions

[Christian F. Howes]

a couple of thoughts...

1. i don't know for sure about datastore connecting to GCE, but the beta 
managed VMs project allows you to run a GCE instance with full connection 
to the app engine datastore (and other services).  We have used it well in 
python for types of processing that we couldn't run on regular app engine 
instances.
2. i don't know if there are limit on datastore entity kinds per project.
3. i like your approach 1 as it seems much easier to code and use to me.

just my 3 cents...

cfh

On Sunday, January 31, 2016 at 5:14:28 AM UTC-8, Dhanunjaya Naidu. Yandrapu 
wrote:
>
> Hi,
>
> I am new to Google cloud and have few question. I have few questions. I 
> would very much appreciate if you could answer them.
>
> we are planning to use appengine, datastore/cloud storage and golang for 
> my next project.Here are my questions:
>
>1. Currently planning to use appengine but might move to compute 
>engine at a later point of time. is it possible to move from appengine to 
>compute engine and seamlessly access datastore and cloud storage from 
>compute engine(in the same project)?
>2. Are there any limits on datastore entity kinds per project?
>3. I would also like to know your thoughts on the following design 
>choice for the data model in datastore. We are planning to use name-spaces 
>for multi-tenancy and we have around 100 entity kinds. I am wondering if 
> *Approach 
>2 *has any advantages over *Approach 1* in terms of query performance 
>or reducing the query cost or deleting all the entities of a particular 
>tenant
>   - *Approach 1*: have 100 entity kinds and use name-spaces for 
>   tenant isolation. So we always have 100 entity kinds regardless of the 
>   number of tenants
>   - *Approach 2*: use name-spaces for tenant isolation and append 
>   tenant ID for each kind, so if we have 10,000 tenants, we will have 1 
>   million entity kinds.
>
> thanks in advance.
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5240eee3-4f6a-4fe0-bea6-0c14aa378a77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Best dashboard to see real time google app engine status: datastore issue

[Christian F. Howes]

i don't know of a better place to check on system status.

most of the time when i have these sorts of errors it is because i had a 
spike in traffic, or newer code is finally hit by our users.  though 
sometimes there are slowdowns in the overall system.

can you check on request load to see if you had a spike?  any chance that 
your logs can help see if it was a DB slowdown or if your java instances 
were performing poorly during that time period?

On Wednesday, January 20, 2016 at 7:49:51 PM UTC-8, Mauricio Lumbreras 
wrote:
>
> Hello,
> 20th jan, 9pm , gmt -3 , we suffered 10 minutes of datastore issues, 
> receiving too much datastore contention exceptions. mostly it was an outage.
> Requests solved usually in a matter of milliseconds -during the issue- 
>  demanded more than one minute and then we get an exception at the end.
> If we go to https://status.cloud.google.com all was ok
>
> Is there a better dashboard to get the actual and updated status of the 
> GAE infrastructure?
>
> We are using app engine, java and mysql
>
> Regards
> Mauricio
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/05a38b11-aa96-4b1e-b3d4-9ad82359817a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Taskqueue Failing with Error Code 123 Before 10 Minute deadline

[Christian F. Howes]

is there any chance that deferred tasks are somehow treated differently 
then regularly queued tasks?  in theory i would think they are just tasks 
with a special handler, but could that be why you are hitting an incorrect 
deadline?

On Wednesday, January 20, 2016 at 7:27:01 AM UTC-8, Nicholas (Google Cloud 
Support) wrote:
>
> Thank you for posting your error logs. According to 'Google Cloud Status 
> ', there are no know outages for Task 
> Queues or App Engine modules at the moment.
>
> As you've mentioned, the default deadline for a automatic scaled modules 
> is 10 minutes. This is documented in 'Task deadlines 
> '.
>  
> Please note that the deadline can be as high as 24 hours for manual or 
> basic scaling modules. Also note that the DeadlineExceededException is 
> raised when the task's execution time nears the deadline, thus allowing you 
> to save your work or log something before the deadline is actually 
> exceeded. That being said, more information is required to get a better 
> idea of what might really be the culprit here:
>
>1. What is the .yaml configuration for the related task-handling 
>modules? (feel free to censor any project-sensitive data)
>2. What is the time frame? (When did this start; is it ongoing; if 
>not, when did it end)
>3. Have you encountered any other timeout or deadline exceeded errors 
>from other modules, including those unrelated to task queues?
>4. How is your queue.yaml configured 
> for the 
>queues experiencing these issues?
>5. Do retries 
>
> 
>  or 
>increased module scalability help reduce the frequency of these errors?
>
> Though the thread 'Suddenly App Engine not Serving Anymore: Error Code 123 
> '
>  
> seems to describe similar errors, the scope of these errors and what 
> systems are causing them is unclear in said thread so I would advise to 
> continue here going forward.
>
> On Tuesday, January 19, 2016 at 9:01:51 PM UTC-5, Michael Sander wrote:
>>
>> Hi All,
>>
>> Over the past few days I've been getting a lot of Error Code 123 in my 
>> Taksqueue. I understand that this error is a deadline, but Taskqueues are 
>> supposed to live for 10 minutes, and I get this error far before that. It 
>> is difficult to debug because these requests have practically no logging 
>> information in them. My app normally spits out a lot of logs, so either GAE 
>> is dropping my logs or this crash occurs outside of my code.
>>
>>
>>1. 2016-01-19 20:36:45.991 /_ah/queue/deferred 500 190547ms 0kb 
>> AppEngine-Google; 
>>(+http://code.google.com/appengine) module=default version=18
>>
>>0.1.0.2 - - [19/Jan/2016:17:36:45 -0800] "POST /_ah/queue/deferred 
>> HTTP/1.1" 500 0 "http://docketupdate.appspot.com/_ah/queue/deferred; 
>> "AppEngine-Google; (+http://code.google.com/appengine)" 
>> "docketupdate.appspot.com" ms=190547 cpu_ms=0 cpm_usd=0.65 
>> queue_name=default task_name=37491651647795200701 exit_code=123 
>> app_engine_release=1.9.31 instance=00c61b117c4864f5a842a8ae7ca496d20dbaa9f8 
>> 
>>
>>2. E2016-01-19 20:36:45.991
>>
>>Process terminated because the request deadline was exceeded. (Error code 
>> 123)
>>
>>
>>
>> Here's another:
>>
>>
>>
>>1. 2016-01-19 19:48:58.581 /_ah/queue/deferred 500 84488ms 0kb 
>> AppEngine-Google; 
>>(+http://code.google.com/appengine) module=default version=18
>>
>>0.1.0.2 - - [19/Jan/2016:16:48:58 -0800] "POST /_ah/queue/deferred 
>> HTTP/1.1" 500 0 "http://docketupdate.appspot.com/_ah/queue/deferred; 
>> "AppEngine-Google; (+http://code.google.com/appengine)" 
>> "docketupdate.appspot.com" ms=84489 cpu_ms=0 queue_name=indexsearch 
>> task_name=5718499252586827456 exit_code=123 app_engine_release=1.9.31 
>> instance=00c61b117cbebad1360673a661a18cf0e69c7cb0 
>> 
>>
>>2. E2016-01-19 19:48:58.580
>>
>>Process terminated because the request deadline was exceeded. (Error code 
>> 123)
>>
>>
>>
>>
>> And another:
>>
>>
>>1. 2016-01-19 19:48:58.583 /_ah/queue/deferred 500 105886ms 0kb 
>> AppEngine-Google; 
>>(+http://code.google.com/appengine) module=default version=18
>>
>>0.1.0.2 - - [19/Jan/2016:16:48:58 -0800] "POST /_ah/queue/deferred 
>> HTTP/1.1" 500 0 "http://docketupdate.appspot.com/_ah/queue/deferred; 

[google-appengine] Re: Image upload problem with GAE SDK running wordpress

[Christian F. Howes]

hmmm, i don't have experience with wordpress and blobstore, we are using 
wordpress and Google Cloud Storage and it works just fine with the (i think 
it is google provided) wordpress GCS plugin.  would switching to that be an 
option for you?

On Wednesday, January 20, 2016 at 9:30:55 AM UTC-8, Ed Nunez wrote:
>
> I'm looking for assistance with an issue I've encountered trying to view 
> uploaded images in wordpress powered by google app engine SDK.
> The images seem to be properly stored in the blobstore provided by the SDK 
> but the image URLs seem to be wrong.
>
> Please see my stackoverflow question for more details.
>
>
> http://stackoverflow.com/questions/34665653/uploaded-images-url-are-incorrect
>
> Respond here or there, wherever you prefer. Thanks!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/08a6fe0c-5a53-478f-934a-8b97a30b9961%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: unexpected image API failure

[Christian F. Howes]

i would start by comparing my permissions on the 2 buckets.  perhaps there 
is a service account or something that needs permission on the bucket that 
is not working?

On Monday, January 18, 2016 at 4:05:57 AM UTC-8, John Smith wrote:
>
> I have created a new bucket and everything seems to work.
> The old bucket does not work, but I still need to use it.
> How can I fix this?
>
> On Sunday, January 17, 2016 at 8:23:23 PM UTC+2, John Smith wrote:
>>
>>
>> Hey,
>>
>> Today I have introduced a new feature in my application which includes 
>> the image.ServeURL() API call.
>>
>> Unfortunately every call to this API returns an error:
>> "API error 1 (images: UNSPECIFIED_ERROR)"
>>
>> This happens in my production environment but I fail to reproduce it on 
>> my development environment (also deployed to the app engine).
>> As far as I can tell everything is exactly the same in these two 
>> environments.
>>
>> Relevant piece of code:
>>
>> blobkey := fmt.Sprintf("/gs/%s/%s", bucketName, fqdn)
>> blobKey, err := blobstore.BlobKeyForFile(ctx, blobkey)
>> if err != nil {
>> return fmt.Errorf("blobkey failure: %v", err)
>> }
>> servingURL, err := image.ServingURL(ctx, blobKey, 
>> {Secure: true})
>> if err != nil {
>> return fmt.Errorf("ServeURL failure: %v", err) // <-- fails here
>> }
>>
>>
>> May you please help me shed some light or suggest a path to debug this?
>>
>>
>> Thanks,
>> John.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/aebb6da1-ce95-4114-b423-79cfdaa0e31a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Change to Authorized Email Senders for App Engine Email API

[Christian F. Howes]

Thanks for the update!  I have some comments/questions:

 - it took me 2 different browsers and about 4 minutes to find the edit 
button on that page.  also really concerning to me that when in edit mode i 
might be editing other application settings and email addresses.
 - i was going to remove some authorized senders and got a warning that 
linked me here: 
https://cloud.google.com/appengine/docs/java/mail/#Java_Sending_mail  
(which was odd since I have a python project).  This concerned me that it 
seems i have no way to add users unless they are in a google managed 
domain.  While i don't need this functionality right now, it's a 
significant change that should be pointed out to people.

Thanks,

Christian

On Thursday, January 14, 2016 at 5:35:16 PM UTC-8, Karolína Netolická wrote:
>
> Dear App Engine users,
>
> We are making a change to the App Engine Email API that affects which 
> email addresses can send email on behalf of the application.
>
> In the past, the email address of any of the Owners, Editors or Viewers of 
> an application could appear in the “from” field of an email sent by the 
> app, allowing the application to send email on behalf of any of its Owners, 
> Editors or Viewers.
>
> We recently separated the concept of Owners/Editors/Viewers and Authorized 
> Email Senders. If you would like to use the email address of a project 
> Owner, Editor or Viewer as the “from” address in an email sent by your 
> application, the Owner/Editor/Viewer’s email address now needs to appear on 
> the Email API Authorized Email Senders list 
> .
>
> To prevent breaking existing email campaigns, we have pre-populated the 
> Authorized Senders list with the email addresses of all Owners, Editors and 
> Viewers on the project. As a result, your existing email campaigns should 
> continue to run normally. To verify that your existing campaigns will not 
> be affected, you can check that the Authorized Email Senders list 
>  for your 
> application contains the address you send email from. 
>
> In the event that you do notice issues with your emails, all you need to 
> do is add the “from” address of the email to the Authorized Senders list. 
> To prevent email spoofing, there are some restrictions on who can add whom 
> to the Authorized Senders list; they are documented here: python 
> , java 
> , go 
> , php 
>  (the logic is the 
> same in all cases). 
>
> Thank you,
>
> Karolina (App Engine PM)
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a1aff3d6-84ea-46a2-80e4-aa2aafd7d48e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Logs viewer broken for one of my projects

[Christian F. Howes]

as a potential work-around next time, remember that the old logs viewer is 
still active while these final issues in the new one get worked out:  
https://appengine.google.com/logs


On Thursday, January 14, 2016 at 2:19:03 PM UTC-8, Jay wrote:
>
> I deployed a new version and that seemed to resolve it.
>
> On Thursday, January 14, 2016 at 3:56:12 PM UTC-6, Jay wrote:
>>
>> The background ajax loader for the logs viewer keeps getting 500 errors. 
>> It won;t load the logs for me at least on one particular project. I have 
>> checked other projects and the logs are loading ok. 
>> Project id in question is atlas-filmdb
>>
>> Thanks for any help. Totally dead without the logs.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/fdf03acf-50fe-4e61-b6ad-c85c29be81f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Exceeded Soft Private memory usage of 128MB

[Christian F. Howes]

FYI, if you use NDB there is a memory leak:  
https://code.google.com/p/googleappengine/issues/detail?id=9610  the google 
folks are having trouble pinning it down, but it's there.  i just let my 
instances restart as they run out of memory as i have not been able to find 
my other memory leaks (i'm sure i have more then just the NDB leak).

On Friday, January 15, 2016 at 9:50:24 AM UTC-8, Kaan Soral wrote:
>
> I have an app that kills instances after just 30 requests sometimes, it 
> functions perfectly tho, the instances die pretty gracefully, my assumption 
> is that they don't take anything with them, rather handle all their 
> requests and die after that
>
> I don't upgrade to F2 as it increases the costs significantly, it's harder 
> to utilise F2 instances efficiently
>
> My .02
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5da29c5c-744d-460a-b9b1-dea911fc29a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How to identify unused data store index?

[Christian F. Howes]

I have not found a great way to do that either.  we have a mirrored test 
server setup that we sometimes delete indexes from and see if anything 
crashes.  not a great solution thoughbut aside from exercising all the 
queries that your code runs there is nothing that can detect if an index is 
missing.

cfh

On Wednesday, January 13, 2016 at 7:50:16 PM UTC-8, A. Kong wrote:
>
> Hi all,
>
> Over time I have a number of indexes in the index.yaml . Some of them may 
> be no longer needed because over time my application ceases to make a 
> certain query.
>
> Is there an easy way to identify unused indexes?
>
> Cheers
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7d0eabeb-f134-4756-a576-b1a8573b195a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: managed vms deployment errors

[Christian F. Howes]

Hi John,

I really don't know about setting up a new project, i haven't done it in a 
while, but can you try an experiment and rename your module?  GAE used to 
have something that was controlled from backend.yaml or backends.yaml 
(can't remember which) and perhaps that is still a sort of keyword.

good luck!

cfh

On Thursday, January 14, 2016 at 5:28:07 AM UTC-8, John Smith wrote:
>
> Today I have created a new project (referenced here as *my-app-id*) in my 
> account and attempted to deploy my code.
>
> using this command:
>
>> aedeploy gcloud preview app deploy --promote backend.yaml --verbosity 
>> debug
>
>
> I have got the following output:
>
> DEBUG: Running gcloud.preview.app.deploy with Namespace(
> __calliope_internal_deepest_parser=ArgumentParser(prog=
> 'gcloud.preview.app.deploy', usage=None, description="*(BETA)* This 
> command is used to deploy both code and configuration to the App 
> Engine\nserver.  As an input it takes one or more ``DEPLOYABLES'' that 
> should be\nuploaded.  A ``DEPLOYABLE'' can be a module's .yaml file or a 
> configuration's\n.yaml file.", version=None, formatter_class= 'argparse.HelpFormatter'>, conflict_handler='error', add_help=False), 
> account=None, authority_selector=None, authorization_token_file=None, 
> bucket=None, cmd_func= calliope.backend.Command object at 0x02E67B50>>, command_path=['gcloud', 
> 'preview', 'app', 'deploy'], configuration=None, deployables=[
> 'backend.yaml'], docker_build=None, document=None, force=False, format=
> None, h=None, help=None, http_timeout=None, image_url=None, log_http=None, 
> project=None, promote='true', quiet=None, repo_info_file=None, server=None
> , stop_previous_version=None, trace_email=None, trace_log=False, 
> trace_token=None, user_output_enabled=None, verbosity='debug', version=
> None).
> DEBUG: API endpoint: [https://appengine.googleapis.com/], API version: 
> [v1beta4]
> You are about to deploy the following modules:
>  - my-app-id/default (from [C:\Users\username\AppData\Local\Temp\
> aedeploy188210551\backend.yaml])
>  Deployed URL: [https://my-app-id.appspot.com]
>
>
> Do you want to continue (Y/n)?  Y
>
>
> Beginning deployment...
> DEBUG: Host: appengine.google.com
> DEBUG: _Authenticate configuring auth; needs_auth=False
> DEBUG: Sending request to https://
> appengine.google.com/api/vms/prepare?app_id=my-app-id 
> headers={'X-appcfg-api-version': '1', 'content-length': '0', 
> 'Content-Type':'application/octet-stream'} body=
> INFO: Attempting refresh to obtain initial access_token
> INFO: Refreshing access_token
> If this is your first deployment, this may take a while...\DEBUG: Got 
> http error 400.
> DEBUG: Unexpected results: {'status': '400', 'content-length': '86', 
> 'expires': 'Mon, 01 Jan 1990 00:00:00 GMT', 'server': 'Google Frontend', 
> 'cache-control': 'no-cache', 'date': 'Thu, 14 Jan 2016 12:54:01 GMT', 
> 'content-type': 'text/plain'}
> If this is your first deployment, this may take a while...failed.
> WARNING: If this is your first deployment, please try again.
> DEBUG: (gcloud.preview.app.deploy) Server responded with code [400]:
>   (unknown).
>   Failed Project Preparation (app_id='s~my-app-id'). Out of retries.  Last 
> error:
> Traceback (most recent call last):
>   File "C:\Program Files (x86)\Google\Cloud 
> SDK\google-cloud-sdk\lib\googlecloudsdk\calliope\cli.py", line 643, in 
> Execute
> result = args.cmd_func(cli=self, args=args)
>   File "C:\Program Files (x86)\Google\Cloud 
> SDK\google-cloud-sdk\lib\googlecloudsdk\calliope\backend.py", line 1401, 
> in Run
> resources = command_instance.Run(args)
>   File "C:\Program Files (x86)\Google\Cloud 
> SDK\google-cloud-sdk\lib\surface\preview\app\deploy.py", line 350, in Run
> deploy_command_util.DoPrepareManagedVms(gae_client)
>   File "C:\Program Files (x86)\Google\Cloud 
> SDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\app\deploy_command_util.py"
> , line 250, in DoPrepareManagedVms
> gae_client.PrepareVmRuntime()
>   File "C:\Program Files (x86)\Google\Cloud 
> SDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\app\appengine_client.py", 
> line 198, in PrepareVmRuntime
> rpcserver.Send('/api/vms/prepare', app_id=self.project)
>   File "C:\Program Files (x86)\Google\Cloud 
> SDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\app\util.py", line 370, in 
> Send
> response = self._server.Send(*args, **kwargs)
>   File "C:\Program Files (x86)\Google\Cloud 
> SDK\google-cloud-sdk\lib\googlecloudsdk\third_party\appengine\tools\appengine_rpc_httplib2.py"
> , line 286, in Send
> 'Unexpected HTTP status %s' % status)
>   File "C:\Program Files (x86)\Google\Cloud 
> SDK\google-cloud-sdk\lib\googlecloudsdk\third_party\appengine\tools\appengine_rpc_httplib2.py"
> , line 69, in RaiseHttpError
> raise urllib2.HTTPError(url, response_info.status, msg, response_info, 
> stream)
> RPCError: Server responded with code [400]:
>   (unknown).
>   Failed Project Preparation (app_id='s~my-app-id'). Out of 

[google-appengine] Re: Local dev server: 'Task task1 failed to execute' due to ' The resource could not be found.'

[Christian F. Howes]

are you using a fully qualified URL or a relative URL?  i use a relative 
URL and let the taskqueue handler figure it out.

note that you can use secure with URLs accessed by the task queue.

On Thursday, January 7, 2016 at 6:12:08 PM UTC-8, A. Kong wrote:
>
> I did more digging and I realised the url is actually marked as 'secure' 
> in app.yaml. Maybe the task execution fails due to a 302, which is not 
> captured in the log?
>
>
> That's why when I test the url in a browser, it returns OK.
>
>
> So what is the best practice in term of which url to pass to the 
> taskqueue.add?
>
>
> On Friday, 8 January 2016 12:28:58 UTC+11, A. Kong wrote:
>>
>> Hi,
>>
>> When I tried to use taskqueue to execute a task in local dev server, I 
>> encounter the said exception and the task simply fails to be executed.
>>
>> Here is more information:
>>
>>
>> Queue definition:
>>
>>
>> - name: votecounter
>>   rate: 1/s
>>   max_concurrent_requests: 1
>>   target: app
>>
>>
>>
>> Python code:
>>
>> taskqueue.add(url, queue_name='votecounter')
>>
>>
>> Here is the exception stacktrace
>>
>>
>> WARNING  2016-01-08 01:16:41,722 main.py:135] handle 404
>> WARNING  2016-01-08 01:16:41,723 main.py:136] The resource could not be 
>> found.
>> Traceback (most recent call last):
>>   File 
>> "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/lib/webapp2-2.5.2/webapp2.py",
>>  
>> line 1529, in __call__
>> rv = self.router.dispatch(request, response)
>>   File 
>> "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/lib/webapp2-2.5.2/webapp2.py",
>>  
>> line 1265, in default_dispatcher
>> route, args, kwargs = rv = self.match(request)
>>   File 
>> "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/lib/webapp2-2.5.2/webapp2.py",
>>  
>> line 1214, in default_matcher
>> raise exc.HTTPNotFound()
>> HTTPNotFound: The resource could not be found.
>> INFO 2016-01-08 01:16:41,787 module.py:794] app: "POST 
>> /_ah/queue/votecounter HTTP/1.1" 404 1218
>> WARNING  2016-01-08 01:16:41,788 taskqueue_stub.py:1977] Task task1 
>> failed to execute. This task will retry in 0.100 seconds
>>
>> Apparently the same code can run OK on the app engine server. How can I 
>> enable taskqueue in a local dev environment?
>>
>> Cheers
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/97e0e6b6-e200-4ea6-82e8-5dd5984a609e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Updating the dispatch file do not work

[Christian F. Howes]

https://appengine.google.com/dispatch

it's in the old console still it seems.  i have no idea where to find it in 
the new console or if it has made it there yet. :(

cfh

On Thursday, January 7, 2016 at 2:24:35 AM UTC-8, Renato Forti wrote:
>
> Where can I find this information on the console?
>
>
> <https://lh3.googleusercontent.com/-_djzcwM-gSc/Vo483Rmmd-I/BXo/_mnmLp2TfAw/s1600/Capture.PNG>
>
>
> On Wednesday, January 6, 2016 at 11:42:54 PM UTC-2, Christian F. Howes 
> wrote:
>>
>> check your dispatch rules in the console just to triple check that they 
>> are uploaded.
>>
>> also check the logs on all your modules to see if you can find where the 
>> request did get routed and that might help you debug.
>>
>> cfh
>>
>> On Wednesday, January 6, 2016 at 9:45:51 AM UTC-8, Renato Forti wrote:
>>>
>>> Hi All,
>>>
>>> I am trying to update the  dispatch file. I have a EAR structure like 
>>> this:
>>>
>>> default(frontend) and dfe(site-dfe) modules
>>>
>>> My dispatch :
>>>
>>> 
>>> 
>>> 
>>>   */favicon.ico
>>>   default
>>>   
>>>   
>>>   dokcloud-1069.appspot.com/
>>>   default
>>>   
>>>   
>>>   */dfe/*
>>>   site-dfe
>>>   
>>> 
>>>
>>> when I try to update I see:
>>>
>>> E:\project.dokfile.vses\hades\trunk\products\dokcloud\cloud\google\frontend\v1\src\main\webapp>appcfg
>>>  
>>> update_dispatch .
>>> Reading application configuration data...
>>> Jan 06, 2016 3:00:45 PM 
>>> com.google.apphosting.utils.config.IndexesXmlReader readConfigXml
>>> INFO: Successfully processed .\WEB-INF/datastore-indexes.xml
>>>
>>>
>>> Beginning interaction for module default...
>>> 0% Uploading dispatch entries.
>>> Success.
>>> Cleaning up temporary files for module default...
>>>
>>> But, this do not work, when I try accees page, 
>>>
>>> *http://dokcloud-1069.appspot.com/dfe 
>>> <http://dokcloud-1069.appspot.com/dfe>*
>>>
>>> I get error:
>>>
>>> Error: NOT_FOUND
>>>
>>> Any Idea?
>>>
>>> Thanks a lot
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/dc94356a-fdd7-4ac5-b5b3-d69a374424c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Updating the dispatch file do not work

[Christian F. Howes]

check your dispatch rules in the console just to triple check that they are 
uploaded.

also check the logs on all your modules to see if you can find where the 
request did get routed and that might help you debug.

cfh

On Wednesday, January 6, 2016 at 9:45:51 AM UTC-8, Renato Forti wrote:
>
> Hi All,
>
> I am trying to update the  dispatch file. I have a EAR structure like this:
>
> default(frontend) and dfe(site-dfe) modules
>
> My dispatch :
>
> 
> 
> 
>   */favicon.ico
>   default
>   
>   
>   dokcloud-1069.appspot.com/
>   default
>   
>   
>   */dfe/*
>   site-dfe
>   
> 
>
> when I try to update I see:
>
> E:\project.dokfile.vses\hades\trunk\products\dokcloud\cloud\google\frontend\v1\src\main\webapp>appcfg
>  
> update_dispatch .
> Reading application configuration data...
> Jan 06, 2016 3:00:45 PM 
> com.google.apphosting.utils.config.IndexesXmlReader readConfigXml
> INFO: Successfully processed .\WEB-INF/datastore-indexes.xml
>
>
> Beginning interaction for module default...
> 0% Uploading dispatch entries.
> Success.
> Cleaning up temporary files for module default...
>
> But, this do not work, when I try accees page, 
>
> *http://dokcloud-1069.appspot.com/dfe 
> *
>
> I get error:
>
> Error: NOT_FOUND
>
> Any Idea?
>
> Thanks a lot
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/febb6dfd-9826-4795-83a5-9aab2e0abe2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Trouble in understanding cost for Projection Query

[Christian F. Howes]

i suspect the docs meant to say "1 Read Operation per row"  i don't know 
how you could ever get to less then 1 read operation per row.

On Thursday, December 17, 2015 at 5:53:07 PM UTC-8, NAyAN Jain wrote:
>
> I am trying to reduce the datastore cost by using Projection. I have read 
> that a Projection Query costs only 1 Read Operation but in my case the 
> Projection cost goes more than 1. Here is the code:
>
>   Query q = 
> ofy().load().type(Finders.class).project("Password","Country");
>   for(Finders finder:q)
>   {
>   resp.getWriter().println(finder.getCountry()+" 
> "+finder.getPassword());
>   }
> On executing this, the q object contains 6 items and to retrieve these 6 
> items it takes 6 Read operations as shown in Appstats. Can anyone tell me 
> what's wrong over here ?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/14da2fa4-115f-484e-8cdc-c319706009a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Contention happens using Task Queue

[Christian F. Howes]

is the object part of an entity group?  there is a limit on the number of 
writes to an entity group (with or without transactions)

On Tuesday, December 15, 2015 at 12:02:23 PM UTC-8, Yun Li wrote:
>
> And there is NO transaction at all. We don't use transaction. But I am not 
> sure if objectify uses the transaction in put. 
>
> On Thursday, December 3, 2015 at 9:59:00 PM UTC-8, Jeff Schnitzer wrote:
>>
>> You'll need to post some more code details - including the structure of 
>> the object you are trying to change. Also you don't mention whether this is 
>> an exception or just a log message. It's easy to accidentally create 
>> contention with the task queue, especially if you're in a transaction and 
>> enqueueing non-transactional tasks (which often start immediately).
>>
>> Jeff
>>
>> On Thu, Dec 3, 2015 at 6:14 PM, Yun Li  wrote:
>>
>>> I am using Objectify. This error happens when updating a single 
>>> datastore entity. There is NO TRANSACTION. My working flow as follows:
>>>
>>> 1 Entity entity1 = Objectify.read(id1)
>>> 2 Modify entity1's property and put "update(entity1)" in a taskqueue
>>> 3 When task executes: Objectify.save(entity1)
>>>
>>> Then I get java.util.ConcurrentModificationException: too much 
>>> contention on these datastore entities
>>>
>>> It's so weird because the log shows that even two requests try to update 
>>> entity1, their execution interval could be more than 10s. I am a new GAE 
>>> user, anybody helps me ?
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to google-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/google-appengine.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-appengine/52790fdf-d521-4f95-b35d-217bcbe2379c%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2458aff1-2214-466e-ac65-ca2e987a21ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Completely removing an application

[Christian F. Howes]

I'm confused. you can indeed start over with your GAE deployments.  each 
deploy replaces what is there, and even if the default version of the 
default module can't be deleted it doesn't cost you anything if nothing 
accesses it.  just deploy new code and you are good to go.

See notes on deploying and deleting individual modules here: 
https://cloud.google.com/appengine/docs/python/modules/#Python_Uploading_modules

On Monday, December 14, 2015 at 7:40:49 AM UTC-8, Mark Betz wrote:
>
> Thanks for the responses, guys. I'm pretty amazed that there isn't some 
> straight-forward way to blow away the deployment and start over, short of 
> ditching the project and whatever other resources have been set up in it 
> (datastore, cloudQL, network rules, etc.). 
>
> Appreciate the help. Our CTO wanted us to look at this platform as a 
> potential alternative to Google Container Engine, but this is a 
> deal-breaker for me.
>
>
> On Friday, December 11, 2015 at 7:01:50 PM UTC-5, Mark Betz wrote:
>>
>> Hi guys. We have a couple of Google projects that we work in and today I 
>> accidentally deployed a set of Google App Engine modules into a project 
>> where we only want to run some container engine stuff. I haven't been able 
>> to figure out how to remove them. The version for all of them is 'beta-1' 
>> but if I do...
>>
>> appcfg.py delete_version -A  -V beta-1
>>
>> I get an error "Cannot delete default version of default module."
>>
>> Is there no way to simply remove this deployment?
>>
>> On a related note, and so I don't step on my own foot again, can anyone 
>> clarify the relationship between Google Cloud projects and Google App 
>> Engine applications? I have the Google cloud SDK installed, and at any 
>> given time that is set to some default one of our cloud projects. However 
>> the appcfg.py tool doesn't seem to have an option to specific which project 
>> I want stuff deployed into. Do deployments always go into the default 
>> project? Or is it related somehow to the application id that you choose?
>>
>> Thanks for any help!
>>
>> --Mark
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c1690f03-821f-428b-9789-5abfd22efcd0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Backing Up Datastore frequency

[Christian F. Howes]

i'll share some things based on my interpretation.happy to be educated 
if i get any of this wrong. :)

1.  to my knowledge in 6 years i've never lost data.  there have been 
outages and slowdowns, but i can't recall a single bit of data loss.  
Remember that BigTable (well, i think it's been renamed to Cloud Datastore 
or something) is replicated.  I suppose if you have 0 traffic you might 
get down to 1 copy, but at some traffic level there are at least 2 copies 
of your data.

2. good question.  i assumed multiple data centers in the same region, but 
i don't know that for a fact.

3.  i don't have a sane regime to recommend. :(  sorry.

cfh

On Saturday, December 12, 2015 at 10:29:03 AM UTC-8, Richard Cheesmar wrote:
>
> Hi, All
>
> I have a few of questions regarding data security and sensible backup 
> routines.
>
> 1. How vulnerable are GAE ndb datastores to data loss? Not focusing 
> specifically on any specific reason, more interested though in physical 
> dangers such as power outs or damage to the infrastructure rather than 
> hacking attacks, although this is important too.
>
> 2. Is data for a single app based at one location or shared around Google 
> Cloud data centers? 
>
> 3. What do others recommend as a sane regime for backing up data on the 
> cloud datastore?
>
> Thanks in advance
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9900a92a-30fb-4c5e-a6ca-cac3725fe309%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Completely removing an application

[Christian F. Howes]

mark,

since the move to console.developers.google.com i have not deleted an app 
engine module fully.  but at appengine.google.com you can delete versions 
of a an app engine module.  once all non-default versions are deleted it 
should let you delete the default version (at least it did the last time i 
did it).  i haven't tried to delete a module from appcfg.py

cloud projects as i understand them...  each GAE application ID is 
associated with a cloud project.  so i think that the app ID that appcfg.py 
uses is a one to one mapping to cloud project ID.  hopefully someone will 
correct me if i'm wrong.

cfh

On Friday, December 11, 2015 at 4:01:50 PM UTC-8, Mark Betz wrote:
>
> Hi guys. We have a couple of Google projects that we work in and today I 
> accidentally deployed a set of Google App Engine modules into a project 
> where we only want to run some container engine stuff. I haven't been able 
> to figure out how to remove them. The version for all of them is 'beta-1' 
> but if I do...
>
> appcfg.py delete_version -A  -V beta-1
>
> I get an error "Cannot delete default version of default module."
>
> Is there no way to simply remove this deployment?
>
> On a related note, and so I don't step on my own foot again, can anyone 
> clarify the relationship between Google Cloud projects and Google App 
> Engine applications? I have the Google cloud SDK installed, and at any 
> given time that is set to some default one of our cloud projects. However 
> the appcfg.py tool doesn't seem to have an option to specific which project 
> I want stuff deployed into. Do deployments always go into the default 
> project? Or is it related somehow to the application id that you choose?
>
> Thanks for any help!
>
> --Mark
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e7d84243-d9bb-421e-8798-58015d105483%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: New Google App Engine Console - Enitity number problems

[Christian F. Howes]

where are you getting the total numbers from?  there is a place that i know 
is an estimated number of entities that is updated by google on a best 
effort basis.  aside from paging through all the rows in the datastore, i 
don't know of any place in the console where the entity counts are expected 
to be up-to-the-minute synced with the datastore.

cfh

On Friday, December 11, 2015 at 10:59:37 AM UTC-8, Richard Cheesmar wrote:
>
>
> Hi, All,
>
> Has anyone noticed a mismatch in the number of entity records recorded in 
> the ndb datastore as opposed to the actual number. I have provided feedback 
> via the console but I have a mismatch - an entity named RealEstate is 
> actually reported as having 134 records when there are actually 141.
>
> Any ideas?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/efdf2272-1d35-4aef-9c16-608f54bb7a3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Do background threads prevent instances created with basic scaling from getting shut down?

[Christian F. Howes]

interesting question - where i have used background threads i have done so 
on manually scaling instances.

on our manually scaling instances we have successfully used the modules API 
https://cloud.google.com/appengine/docs/python/refdocs/google.appengine.api.modules.modules
 
to control startup and shutdown of instances.  I think this can be used to 
forcibly shutdown an autoscaling instance as well.

Hope that helps!

cfh

On Wednesday, December 9, 2015 at 1:17:16 AM UTC-8, Erik Kuefler wrote:
>
> The description of basic scaling 
> 
>  
> is a little vague about the exact conditions that cause an instance created 
> with basic scaling to be shut down. It says an instance is evicted when it 
> "has not received a request for more than `idle-timeout`", but it's not 
> clear to me whether this includes background threads and the 
> "/_ah/background" request that they generate.
>
> My problem is that my machines are staying alive longer than I expect them 
> to and I suspect a background thread might be the culprit. I'm using a 
> library (Firebase) that creates background threads but provides no way of 
> shutting them down. Will this cause my machines to never be evicted? If so, 
> is there a way for me to either forcibly terminate all background threads, 
> or to shut down the instance from my own background thread (so I can 
> implement my own idle timeout)?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f2835db7-f931-40e0-8b6a-b6c4739f0ddb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Routing with dispatch.yaml not working from within app

[Christian F. Howes]

I'll agree that i have seen similar issues and now as a matter of habit 
always specify my intended target when queuing tasks.

It would be great to update the documentation to make that more obvious. :)

cfh

On Friday, December 4, 2015 at 1:53:52 PM UTC-8, Adam wrote:
>
> You can try using the target 
>  
> parameter to explicitly specify the module the task should run on. 
> According to the docs, the HTTP *may* be intercepted by the dispatch 
> routing rule, so this seems to imply it doesn't always happen.
>
> Cheers,
>
> Adam
> Cloud Platform Support
>
> On Wednesday, December 2, 2015 at 6:57:03 PM UTC-5, Kirill Kireyev wrote:
>>
>> Hi,
>>
>> I have a GAE app with two modules, default and "background". My 
>> dispatch.yaml file says:
>>
>> dispatch:
>>
>>   - url: "*/cron/*"
>>
>> module: background
>>
>>   - url: "*/_ah/queue/deferred"
>>
>> module: background
>>
>>   - url: "*/background_tasks/*"
>>
>> module: background
>>
>>
>> When I enter a "http://MYHOST/background_tasks/XXX; from my web browser, 
>> the task is indeed handled by the "background" module.
>>
>>
>> However, when the task is run from within my app:
>>
>> taskqueue.add(url="/background_tasks/XXX"), queue_name="YYY")
>>
>>
>> The task is handled by the default module (I've verified this by looking 
>> at the GAE logs in Dev Console for each of the two modules separately).
>>
>>
>> Can someone please help me understand why this discrepancy?
>>
>>
>> Thanks,
>>
>> Kirill
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/718a6565-1ec7-438a-9c4b-04cea1c647b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Loading data into automatic scaled instance memory

[Christian F. Howes]

can you slice up your data into 1mb chunks that you can load into the app 
engine memcache?  we do that a lot with our data and use expiration times 
to evict keys and trigger re-loads quite a lot in our system.

cfh 

On Thursday, November 5, 2015 at 4:42:49 AM UTC-8, John Smith wrote:
>
> Each instance of my application module (default) needs to load data from 
> the datastore into local memory (for performance/cost reasons), where it 
> will be read-only.
> A separate module updates the data in the datastore (updater), and the 
> data needs to be refreshed (entirely) in each default instance every 
> several minutes (preferably when the data is updated by the updater module).
> Loading the data into instance memory takes more time than is reasonable 
> for a single user request.
>
> I would have used a thread (goroutine) with a background context to reload 
> the data in each (default) instance, but background context is not 
> supported in automatically scaled modules.
>
> How should I update each (default) instance's memory when the data is 
> updated by the updater module?
>
> I am using the go runtime environment.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ca5c82ba-bbe0-46d0-8a47-927578efc909%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Anyway create a system log of admins who have signed onto the app engine console ?

[Christian F. Howes]

Yun,

do you know about the admin logs?

https://appengine.google.com/adminlogs?_id=s~

in the old GAE console you can find a link in the left side bar to the 
admin logs.  I don't know if that is exactly the information that you are 
looking for, but it might be some of it.

Christian

On Monday, November 9, 2015 at 6:15:15 PM UTC-8, Yun Li wrote:
>
> Enable me to see every develop's activity.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4797549a-1a66-4c41-afb9-6cffcce901e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Stop Backend from new Admin Console

[Christian F. Howes]

bummer.  I don't have an answer for you - the last of my backends were 
deleted a couple of months ago.


I hear you on how changes cascade!

christian

On 10/20/15 02:11, Alejandro Gonzalez wrote:

I know backends are deprecated... forget about them (thinking in the
refactor i need to made and how it will affect to my CI flow, build scripts
and app versioning approach...)

If I have a module deployed to a version (v1-2-54-back) and configured to
have 2 resident instances: can i stop that module version from the admin
console so it does not start more instances (without deleting it so i can
re-activate it)?

Maybe i need to rethink my versioning and deployment processes a bit... i
will start another specific thread for this if i need advice (I bet i will
:D)


El martes, 20 de octubre de 2015, 1:35:10 (UTC+2), Christian F. Howes
escribió:


note that i was reminded by google support recently that backends are a
deprecated feature, so i bet managing them in the new console won't ever
come. :(

the modules with manual scaling ("B1" etc. instance classes) work great,
and we have found them much easier to manage (the logs are separated from
other modules, the deployments are much smoother for us).

Good luck!

Christian

On Monday, October 19, 2015 at 2:49:21 AM UTC-7, Alejandro Gonzalez wrote:


Hello,

I have an application that still uses backends instead of modules. In the
new Admin Console there is no section for backends, therefore there is a
feature that i can't use: stop a backend.

Stop a backend means that that backend version stops starting instances
and this is very important when the backend is configured to have 2
resident instances and you use an incremental version number approach when
deploying backends.

In the new console is there a feature to prevent a version create new
instances?

Thanks.






--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/562666B9.90702%40starmakerinteractive.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Stop Backend from new Admin Console

[Christian F. Howes]

note that i was reminded by google support recently that backends are a 
deprecated feature, so i bet managing them in the new console won't ever 
come. :(

the modules with manual scaling ("B1" etc. instance classes) work great, 
and we have found them much easier to manage (the logs are separated from 
other modules, the deployments are much smoother for us).

Good luck!

Christian

On Monday, October 19, 2015 at 2:49:21 AM UTC-7, Alejandro Gonzalez wrote:
>
> Hello,
>
> I have an application that still uses backends instead of modules. In the 
> new Admin Console there is no section for backends, therefore there is a 
> feature that i can't use: stop a backend. 
>
> Stop a backend means that that backend version stops starting instances 
> and this is very important when the backend is configured to have 2 
> resident instances and you use an incremental version number approach when 
> deploying backends.
>
> In the new console is there a feature to prevent a version create new 
> instances?
>
> Thanks.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/aa12ab10-8fd1-4dfc-aa96-e820800fdf5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: App Engine admin console redirects to Developers Console

[Christian F. Howes]

Deepak,

Just hitting the logs console via 
https://console.developers.google.com/project//logs often hangs 
and never loads.  I have been frequently having to force refresh the 
page several times before the logs load.  then any query also takes a 
long time to load.


thanks for the help!

christian

On 10/8/15 07:59, Deepak Tiwari wrote:

Hi Mark,
I am the PM for Cloud Logging.  Thank you for the feedback on the logs
viewer.  We are looking at UI design options for proving the best option
for viewing the log lines in the collapsed format.  Your feedback is
valuable.  On the slowness of the logs viewing - we are actively looking at
this as well to fix this issue.  If you can tell me a little more about the
query you are running that is taking time that would be very helpful.
Thanks,
Deepak

On Wednesday, October 7, 2015 at 11:42:55 AM UTC-4, Mark Cummins wrote:


The new logs viewer is much less usable. Because it's either totally
collapsed or totally expanded, it's much much harder to extract meaningful
patterns of events at a glance. I would really like to get back the
single-line-per-message view that the old viewer had.
Also, it seems slower to display first logs.

On Wednesday, 7 October 2015 11:01:20 UTC+1, Stewart Fife wrote:


Hello!

We are pleased to announce that we redirected the first set of App Engine
admin console menus to Developers Console today. This begins the final
stage of consolidating the management of Google Cloud Platform services
into one consistent experience for customers.

Thanks for all your feedback on this important change.

Stewart on behalf of the GAE team







--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5616A3EA.2090500%40starmakerinteractive.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: App Engine admin console redirects to Developers Console

[Christian F. Howes]

Deepak,

Thanks for looking into this.  For the broader group - i'm using Chrome 
on Mac right now.  It may just be that I am impatient and that the logs 
would eventually load, but give up after about 30 seconds.  It does not 
happen 100% of the time.


thanks,

christian

On 10/8/15 10:31, 'Deepak Tiwari' via Google App Engine wrote:

Hi Christian,

Thanks for the feedback.  I just tried it for my projects and seems to work
fine.  What browser are you using?

I'll ping you separately - it'd be good to get your project name for us to
look into it.

Thanks,
Deepak

On Thu, Oct 8, 2015 at 1:12 PM, Christian F. Howes <
christian.ho...@starmakerinteractive.com> wrote:


Deepak,

Just hitting the logs console via
https://console.developers.google.com/project//logs often hangs
and never loads.  I have been frequently having to force refresh the page
several times before the logs load.  then any query also takes a long time
to load.

thanks for the help!

christian


On 10/8/15 07:59, Deepak Tiwari wrote:


Hi Mark,
I am the PM for Cloud Logging.  Thank you for the feedback on the logs
viewer.  We are looking at UI design options for proving the best option
for viewing the log lines in the collapsed format.  Your feedback is
valuable.  On the slowness of the logs viewing - we are actively looking
at
this as well to fix this issue.  If you can tell me a little more about
the
query you are running that is taking time that would be very helpful.
Thanks,
Deepak

On Wednesday, October 7, 2015 at 11:42:55 AM UTC-4, Mark Cummins wrote:



The new logs viewer is much less usable. Because it's either totally
collapsed or totally expanded, it's much much harder to extract
meaningful
patterns of events at a glance. I would really like to get back the
single-line-per-message view that the old viewer had.
Also, it seems slower to display first logs.

On Wednesday, 7 October 2015 11:01:20 UTC+1, Stewart Fife wrote:



Hello!

We are pleased to announce that we redirected the first set of App
Engine
admin console menus to Developers Console today. This begins the final
stage of consolidating the management of Google Cloud Platform services
into one consistent experience for customers.

Thanks for all your feedback on this important change.

Stewart on behalf of the GAE team








--
You received this message because you are subscribed to a topic in the
Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/google-appengine/lyodceDDUIU/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/5616A3EA.2090500%40starmakerinteractive.com
.

For more options, visit https://groups.google.com/d/optout.







--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/561731A6.3060106%40starmakerinteractive.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: App Engine admin console redirects to Developers Console

[Christian F. Howes]

I'll add that my team really misses the old console.  A major upside to GAE 
was ease and speed of administration to allow me to have no dev ops on my 
team, and this new console is so much slower and less efficient that it 
will have a major impact on our ability to quickly diagnose things and get 
back to development.  In general the javascript based functions are much 
slower then the older console, it takes more clicks to get to data, and 
fonts are so large in the new console that things no longer fit into single 
screens for fast perusal.  I'm hopeful for many improvements soon!

Christian

On Wednesday, October 7, 2015 at 9:19:18 AM UTC-7, Alex Martelli wrote:
>
> Please add a feature request to the public issue tracker, cfr 
> https://code.google.com/p/googleappengine/issues/list?can=2=Component%3DLogging+Component%3DAdminconsole+=ID+Type+Component+Status+Stars+Summary+Language+Priority+Owner+Log=tiles
>  
> .
>
> Thanks,
>
> Alex
>
>
> On Wed, Oct 7, 2015 at 8:42 AM, Mark Cummins  > wrote:
>
>> The new logs viewer is much less usable. Because it's either totally 
>> collapsed or totally expanded, it's much much harder to extract meaningful 
>> patterns of events at a glance. I would really like to get back the 
>> single-line-per-message view that the old viewer had.
>> Also, it seems slower to display first logs. 
>>
>> On Wednesday, 7 October 2015 11:01:20 UTC+1, Stewart Fife wrote:
>>>
>>> Hello! 
>>>
>>> We are pleased to announce that we redirected the first set of App 
>>> Engine admin console menus to Developers Console today. This begins the 
>>> final stage of consolidating the management of Google Cloud Platform 
>>> services into one consistent experience for customers. 
>>>
>>> Thanks for all your feedback on this important change. 
>>>
>>> Stewart on behalf of the GAE team
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/2695feba-d2b7-4ee1-abde-c2d6f1198fcd%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a6411d69-51bd-4d88-b94b-43cf4a8fde6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Missing custom domain

[Christian F. Howes]

My case was only for my test serversi *think* that the domain 
routing might have been OK, we noticed it when coming back to test 
something under https which was not working until we re-verified and 
re-connected the SSL certs.


cfh

On 10/2/15 08:32, Richard Cheesmar wrote:

Christian, did the re-verification cause downtime for your domain?

On Thursday, October 1, 2015 at 1:30:24 PM UTC+3, Richard Cheesmar wrote:


Hi,

I had two custom domains on my setup. Now one is not there, the domain in
question, www.emlakair.com is still working and pointing to the app
engine code, but missing from the developers console

Please advise as I want to start using SSL asap.

Thank you

Richard Cheesmar





--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/560EB8C8.1080501%40starmakerinteractive.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Missing custom domain

[Christian F. Howes]

also note that just yesterday i noticed the same problem - turns out when 
my custom domains were mapped from google apps to the cloud console, only 
my primary domain made it.  i just had to use the console to add/verify the 
domain and then my settings mostly migrated.  i did have to re-attach my 
SSL certs to the second domain after i verified it (but the certs appeared 
once the domain was added).

hope that helps,

cfh

On Thursday, October 1, 2015 at 4:10:06 PM UTC-7, Nick (Cloud Platform 
Support) wrote:
>
> Hey Richard,
>
> It sounds like you're having a specific technical issue with the Custom 
> Domains feature of the Developers Console. Such issues are best posted to 
> stackoverflow.com, since this forum is meant for more general discussion 
> of the platform. I'd advise you to post screenshots and relevant 
> information such as the DNS records on your domain, when you make your 
> post. We monitor there and there will surely be many other users interested 
> in helping you find a solution. You can find instructions on how to set up 
> a Custom Domain and SSL in our documentation 
> 
> .
>
> On Thursday, October 1, 2015 at 8:45:16 AM UTC-4, Richard Cheesmar wrote:
>>
>> Meant to say, in second post that I have two accounts that were both 
>> setup as owners of the project and the domain name www.emlakair.com has 
>> been verified, except I can't blooming see it...I have tried logging into 
>> the console with both accounts and still only see the other domain, not 
>> www.emlakair.com. 
>>
>> Now, I have recently setup an account on with Google's search console and 
>> both the same owners are specified for the account on their, has this got 
>> something to do with it perhaps?
>>
>> Why is everything so frustrating with Google, can't you just make life a 
>> little bit easier please?
>>
>>
>>
>> On Thursday, October 1, 2015 at 1:30:24 PM UTC+3, Richard Cheesmar wrote:
>>>
>>> Hi,
>>>
>>> I had two custom domains on my setup. Now one is not there, the domain 
>>> in question, www.emlakair.com is still working and pointing to the app 
>>> engine code, but missing from the developers console
>>>
>>> Please advise as I want to start using SSL asap.
>>>
>>> Thank you
>>>
>>> Richard Cheesmar 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/fb048e40-85d8-4f4d-a902-a325e9abb24d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Final release of GAE Managed VMs?

[Christian F. Howes]

For what it's worth, I have been using Managed VM's in a production 
application for several months now.  They usually are pretty good, but we 
just had a rough patch the past 2 weeks as Google is working on 
improvements to the platform.  I'm currently considering going to good 'ol 
GCE instances if i can find a good way to connect task queues, memcache and 
db to a GCE instance.

christian

On Sunday, September 27, 2015 at 4:35:42 PM UTC-7, Alex Martelli wrote:
>
> On Sun, Sep 27, 2015 at 3:55 PM, Uljan Sharka  > wrote:
>
>> Approximately when will be available the final release of Managed VMs?
>>
>
> I don't believe any announcements about this have been made (has Google 
> *ever* pre-announced such dates, even "approximately"?)
>  
>
>> Does it make sense to host production applications on top of this if it 
>> is not covered by any SLA or deprecation policy while in beta?
>>
>
> According to https://cloud.google.com/terms/launch-stages, and I quote:
>
> Beta releases are suitable for limited production use cases
>
> Of course, this is just Google's own opinion, so you'll have to decide on 
> your own, case by case, based on your own judgment and your own detailed 
> understanding of your own situation (would it be a "limited" production use 
> case, or, not "limited"? -- and so forth).
>
>
> Alex
>
>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/7f26314b-fadf-489c-8bd5-503004ccbf2e%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/62fc7b7b-e494-40e6-ab5f-6d47ba36aa0e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Sending email to a Google Group in a Google Apps for Business domain

[Christian F. Howes]

does the sender email address have at least  "viewer" permissions in the 
google cloud console project?  i have been bitten by that a few times

christian

On Monday, September 21, 2015 at 9:10:56 AM UTC-7, Romuald Cari wrote:
>
> Hi,
>
> I've been following this document about how to send email from App Engine 
> using Python: https://cloud.google.com/appengine/docs/python/mail/
> Everything works fine when using the development server with SMTP 
> configured, however, when publishing my app, I never receive any emails.
>
> I'm using the admin account for that Google Apps For Business domain as 
> the sender, an email address that is part of the authorized senders of my 
> application.
> I can't figure out why emails are not delivered to my group.
>
> Thanks in advance for your help.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a835793d-9d9f-4b0c-b43d-fc32e629cd5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Old versions of Managed VMs

[Christian F. Howes]

Hi Jeff,

>From what i can see managed VMs behave much like app engine modules that 
use backend instance class and manual scaling - which means they stay live 
when you deploy a new version, and even after setting default.

I'm still using the "old" app engine console, and when i delete an old 
managed VM instance (or even click the stop link) it will shut down.  It 
does take longer then for an app engine instance - sometimes 10-15mins, but 
i think that has to do with the managed VM health-check timing and shutdown 
process (or perhaps i just have mis-implemented my shutdown handlers on my 
managed VMs).

I hope that helps.

Christian

On Tuesday, September 15, 2015 at 4:15:10 PM UTC-7, Jeff Schnitzer wrote:
>
> I have a python app on a Managed VM which I deploy with:
>
> gcloud preview app deploy app.yaml --remote --set-default
>
> It's set to manual scaling, instances 1.
>
> It appears that every time I deploy it, the old instance stick around (and 
> get billed for). Even deleting the old versions from the appengine console 
> didn't shut down the compute engine instances. I had to figure out which 
> compute engine instance was my "live" one and delete all the others from 
> the Compute Engine part of the console.
>
> Is this supposed to work this way or is there a better workflow? I just 
> want to deploy the new version and have the old version go away... like 
> regular App Engine.
>
> Jeff
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9d38ef2a-2b47-455c-aea4-23b423c06d42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Understanding the value proposition of App Engine for data processing

[Christian F. Howes]

I've found map reduce to be painful, but i don't do tons of large-scale 
data processing.  i do run a mobile application API on app engine and for 
that app engine is simply amazing!  with a carefully designed schema and 
using the limits of app engine to my advantage we get great performance 
without the overhead of managing our own servers.

at this point i'm doing my large scale data crunching in big query (though 
your use case sounds like it might not be easy to fit in there).

christian

On Tuesday, August 11, 2015 at 11:30:03 AM UTC-7, Duo Zmo wrote:

 I'm just digging into map reduce on Google App Engine, and my early 
 results are discouraging. I had in mind that I'd process about 10GB of data 
 for an analysis I want to do, and I didn't even think that'd be that big a 
 deal (given all the talk about petabyte-scale storage and such), but it's 
 currently looking impossible. 

 I did a simple word count mapreduce on some Gutenberg books (63MB zipped, 
 166MB unzipped), once using Google's Python mapreduce example (
 https://cloud.google.com/appengine/docs/python/dataprocessing/) and once 
 using the dumb-as-rocks standalone Python scripts posted at the top of 
 Michael Noll's Hadoop tutorial (
 http://www.michael-noll.com/tutorials/writing-an-hadoop-mapreduce-program-in-python/
 ).

 Experimental results:

 Simple Python: 1 minute 22 seconds
 GAE dev server: 2 hours 17 minutes 12 seconds

 Given the staggering difference in run time, even if computation in the 
 cloud were free, I'd still opt to compute locally unless my hand were 
 forced somehow (e.g. input files that didn't fit on my disk). Of course, 
 the computation is not free, which means you're not only enduring all that 
 overhead, but paying for it too.

 I did try running this same test in production, i.e. on Google Cloud's 
 infrastructure. At first it failed, because just getting the job started 
 exceeded the 128MB memory limit for the free tier. I turned on billing, 
 bumped up the instance class to F4, and let it go. It chewed through the 
 free tier quickly, then about USD$8 of instance time before one of the 
 shuffle-merge shards seemed to enter an infinite loop (ran for 2 hours, no 
 errors in logs). I aborted and gave up at that point.

 Everything I hear about cloud computing makes it sound like the gleaming, 
 glossy future, but these results makes it seem expensive and slow. $8+ to 
 do a mapreduce across 60MB of data just doesn't seem like a good deal to 
 me. At that rate, there's no way I can afford to process my 10GB dataset on 
 App Engine. I understand that with the pipeline model you get fault 
 tolerance and status reports and basic job management, but none of that is 
 worth the expense or a 100x performance hit.

 I think there's two possible problems going on here:

 1) I made a technical mistake in my experiment and my results are invalid
 2) I'm not understanding the benefits / value proposition of App Engine

 Are my results consistent with what others would expect? Do either or both 
 of my candidate explanations ring true? What else am I not considering? I 
 think this is more a discussion topic than a discrete ask-and-answer, which 
 is why I'm posting here instead of Stack Overflow.


-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3207f117-109b-431a-9d5d-0c10c38aa24e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Wrong data storage in GAE NDB

[Christian F. Howes]

depending on how many writes you expect per second, transactions might be 
sufficient to solve the problem.  they are write rate limited, so you may 
still need sharded counters or some other way to batch writes as suggested 
by Ryan.

On Thursday, July 9, 2015 at 4:33:42 AM UTC-7, Ankur Jatt wrote:

 Here is the situation
 I have a model like

 class Content(ndb.Model):
 likeCount=ndb.IntegerProperty(default=0)
 likeUser  = ndb.KeyProperty(kind=User, repeated=True)

 When a new content generate than a new Content object is generated like

 content_obj = Content(parent=objContentData.key, #Where ContentData is 
 another ndb.Model subclass
  likeUser=[],
  likeCount=0
)

 And when any user like the same content than below function gets called

 def modify_like(contentData_key, user_key):
 like_obj = Content.query(parent=contetData_key).get()
 if like_obj:
 like_obj.likeUser.append(user_key)
 like_obj.likeCount += 1
 like_obj.put()

 ###Problem#
 Now the problem is that when at the same time more than 4 user like the 
 same content than this object write wrong data.
 So how can I solve this problem


-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d251106a-0abe-4b33-88ad-76a436d9139b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Shutdown module polling the task queue

[Christian F. Howes]

I use backend instance class for this with manual scaling:

instance_class: B1
manual_scaling:
  instances: 1

and then in the console i click the stop button next to my version.  It 
will stay stopped until you click start again or re-deploy.

for a more dynamic version of that i use push queues, but APNS needs to be 
send int a backend instance.  i have not used it yet, but maybe you can 
send GCM messages with apple targets using the new GCM for iOS announced 
last week: https://developers.google.com/cloud-messaging/ios/client  
perhaps that can run on a frontend instance with automatic scaling and a 
push queue?

On Friday, June 5, 2015 at 2:40:31 AM UTC-7, André Solberg wrote:

 I use Google App Engine as backend for an iOS application. I have a 
 separate module that polls the Task Queue, looking for push notifications 
 queued for sending. The module starts a background thread on /_ah/start and 
 runs as long as the module is running.

 The backend has dynamic availability, so when there are no requests for a 
 while it will go idle. When there are no instances running, there is no 
 need for the polling either. After I added the module, the billing charges 
 has increased a lot because of instance hours usage. I'm still developing 
 the app and the backend, so the backend is idle most of the time. I thought 
 I could at least manually shut down the module and only turn it on when I 
 need it for testing. But the module restarts by itself immediately after I 
 shut it down...


 How can I implement a good cooperation between the default module and 
 the polling module, so that if there are no instances running on the 
 default module, the polling module will automatically shut down?




-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e62de5a4-ad9f-46b4-a736-1a4c12b48fb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google Apps No Longer Free

[André Garcia F . Pinto]

I agree with Philip! For someone who has lots of users/projects to manage
in Engine, it just makes no more sense.

My personal problem was way simpler than that. I just wanted an e-mail
host for my domain but I liked very much the interface by google of
managing domain, my own (and oly) user along with all the resources, like
Google Drive, calendar, contacts, tasks, etc all integrated... also with my
android device.

I have a domain at Namecheap whose e-mail host is OX. Their service is very
good, but there is no integration with contacts and calendar and all the
cloud advantages.

I just was looking for the best way to have my tools and everything somehow
sincronized.

Cheers
André


2015-01-22 8:08 GMT-02:00 Philip Kilner phil.kil...@gmail.com:

 Hi Vinny,

 On 22/01/15 04:22, Vinny P wrote:

 You're talking about the difference between adding the domain as a
 secondary domain/adding it as an alias domain, correct?


 Yes, I think so - don't recall the term secondary, but looking at a paid
 Google apps account, the option is described as: -

 Add another domain
 Manage users and groups at an associated domain that you own,
 independently of the primary domain.

 ...so I think we're talking about the same thing.

  To connect a domain name to App Engine, it's always been recommended to
 use the domain as a primary or an alias domain on Apps. Configuring it
 as a secondary domain might give you distinct email accounts, but in my
 experience that introduces strange issues for Apps management and config
 - not only for App Engine but other services as well. I understand your
 point, but at the same time I think the change helps streamline Apps and
 probably helps reduce support costs as well. Frankly, I've always
 thought it was strange that Apps had 3 different ways (primary,
 secondary, alias) of configuring domains.


 Re. problems, I haven't experienced those, but to be honest that's
 probably because I'm not doing anything very complicated.

 Re. helps streamline Apps and probably helps reduce support costs, I
 don't honestly see that - this change makes the grandafathered free
 versions different from the standard version in functionality as opposed to
 numerical limits (which is surely /less/ streamlined), and given that were
 are talking about the unpaid versions I don't supposed an enormous amount
 of resource goes into support.

 FWIW, although Google have been silent on this issue, there is some
 suggestion in the support forums that this was done to prevent abuse,
 specifically to prevent people selling free apps accounts and using this
 mechanism to switch domains. If that's the case, I'm a little perplexed -
 seems like a crude way of combating the problem, and it seems like a
 problem that is self-limiting in the sense that there can only be a finite
 no. of these account out there. More to the point, I feel as though I'm
 being punished for someone else's misbehaviour, and that Google haven't
 been entirely straight about the fact, the timing, or the rationale for the
 change.

 It might seem churlish complaining about tweaks to a free service, and I
 absolutely do appreciate the fantastic freebie that apps for domains was
 (and continues to be, up to a point), but it does constitute a change when
 we were told the service would be unchanged, and it does make my existing
 accounts much less useful for my purpose, in part because this has
 diminished my confidence in continuity of service.

  If you absolutely must have free email accounts, I would suggest looking
 at your registrar - GoDaddy and other registrars occasionally have sales
 where they bundle free email or another service with the purchase of a
 domain. It's entirely possible to configure an alias domain, use it for
 an App Engine site, but to use an external mail service for that domain.


 Sure - I run a bunch of servers with Virtualmin on them, so giving people
 the ability to create multiple email addresses is not an issue.

 For me the issue is that I was able to set up projects with a domain name,
 probably only two or three users (one of them me), and hand it over the
 user as a coherent whole, where the Google Apps account let them manage
 their domain, email, apps and - in some cases - App Engine apps with a
 single account.

 Knitting together multiple services is fiddly for me, and the result is
 messier for my users. What I've come to realise is that the Google account
 within the Apps domain was the valuable bit - without that, its easier to
 host and deploy elsewhere.

 Having said all the above, I recognise that I'm probably not that great a
 fit for App Engine, and that this change has just made that clear to me -
 my point is merely that this is an unannounced change to the service, and
 that for some of us it means that these grandfathered accounts are no
 longer useful for new projects.


 --

 Regards,

 PhilK


 'a bell is a cup...until it is struck'

 --
 You received this message because you are subscribed 

Re: [google-appengine] Re: Google Apps No Longer Free

[André Garcia F . Pinto]

Thank you Vinny!
Bummer that no other service is available for free.

Other question, then:
Google apps seems to be free for existing users before 2012. I do have a
google apps acount I had for an old domain. If I log in with my previous
account and add my new domain and user there. Would that still be free?

Thanks

André

*André Garcia F. Pinto*
*Whatsapp:* +55 11 9 8272-2012
*Skype:* agfp86
*E-mail:* agfpi...@gmail.com

2015-01-21 5:24 GMT-02:00 Vinny P vinny...@gmail.com:

 On Wed, Jan 14, 2015 at 7:47 AM, André Pinto agfpi...@gmail.com wrote:

 Is it still able to get 1 user per account for free?
 I have bought my domain at Namecheap.com and would like to use Google as
 an e-mail host/providor... for free lol

 Is it still possible? If not, any suggestions on how to? I've also seen a
 possibility to hot at Outlook.com for free via Windows Live... only needs a
 domain and nothing more.



 No, it's not possible. You'll now have to pay for a Google Apps account,
 there's no more freebie 1 user per account provision. As for Windows
 Live Domains, that offer has also been ended.
 http://www.zdnet.com/article/microsoft-ends-support-for-custom-domains-in-free-email-service/


 -
 -Vinny P
 Technology  Media Consultant
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.com

  --
 You received this message because you are subscribed to a topic in the
 Google Groups Google App Engine group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/google-appengine/pVZfdeky-ow/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to
 google-appengine+unsubscr...@googlegroups.com.
 To post to this group, send email to google-appengine@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-appengine.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-appengine/CALSvALB8ChG4Q0%2BG%3DPDm-PLbLjPtBcTQKP7TZ2YosES0S_ZOOQ%40mail.gmail.com
 https://groups.google.com/d/msgid/google-appengine/CALSvALB8ChG4Q0%2BG%3DPDm-PLbLjPtBcTQKP7TZ2YosES0S_ZOOQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAFbOS96MFUuN9Tjdib3BAY5PHUGaBBQdKQ4Lw6X1kURR8Q2ojw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] BadStatusLine when run dev_appserver

[Amaranth F]

My helloworld.py is like this:
def main(environ,start_response):
   response_body = 'The request method was %s' % environ['REQUEST_METHOD']
   status = '200 OK'
   response_headers = [('Content-Type', 'text/plain'),
   ('Content-Length', str(len(response_body)))]
   start_response(status, response_headers)
   return [response_body]

then I ran python dev_appserver.py proj/test succeeded.
but I got a BadStatusLine exception when I goto http://localhost:8080.

Did anyone know how to solve this?

BadStatusLine: ''
Traceback (most recent call last):
  File 
F:\Program\google_appengine\lib\cherrypy\cherrypy\wsgiserver\wsgiserver2
.py, line 1302, in communicate
req.respond()
  File 
F:\Program\google_appengine\lib\cherrypy\cherrypy\wsgiserver\wsgiserver2
.py, line 831, in respond
self.server.gateway(self).respond()
  File 
F:\Program\google_appengine\lib\cherrypy\cherrypy\wsgiserver\wsgiserver2
.py, line 2115, in respond
response = self.req.server.wsgi_app(self.env, self.start_response)
  File 
F:\Program\google_appengine\google\appengine\tools\devappserver2\wsgi_se
rver.py, line 269, in __call__
return app(environ, start_response)
  File 
F:\Program\google_appengine\google\appengine\tools\devappserver2\request
_rewriter.py, line 311, in _rewriter_middleware
response_body = iter(application(environ, wrapped_start_response))
  File 
F:\Program\google_appengine\google\appengine\tools\devappserver2\python\
request_handler.py, line 148, in __call__
self._flush_logs(response.get('logs', []))
  File 
F:\Program\google_appengine\google\appengine\tools\devappserver2\python\
request_handler.py, line 284, in _flush_logs
apiproxy_stub_map.MakeSyncCall('logservice', 'Flush', request, response)
  File 
F:\Program\google_appengine\google\appengine\api\apiproxy_stub_map.py,
line 94, in MakeSyncCall
return stubmap.MakeSyncCall(service, call, request, response)
  File 
F:\Program\google_appengine\google\appengine\api\apiproxy_stub_map.py,
line 328, in MakeSyncCall
rpc.CheckSuccess()
  File F:\Program\google_appengine\google\appengine\api\apiproxy_rpc.py, 
line
156, in _WaitImpl
self.request, self.response)
  File 
F:\Program\google_appengine\google\appengine\ext\remote_api\remote_api_s
tub.py, line 200, in MakeSyncCall
self._MakeRealSyncCall(service, call, request, response)
  File 
F:\Program\google_appengine\google\appengine\ext\remote_api\remote_api_s
tub.py, line 226, in _MakeRealSyncCall
encoded_response = self._server.Send(self._path, encoded_request)
  File 
F:\Program\google_appengine\google\appengine\tools\appengine_rpc.py, li
ne 409, in Send
f = self.opener.open(req)
  File e:\software\python27\lib\urllib2.py, line 404, in open
response = self._open(req, data)
  File e:\software\python27\lib\urllib2.py, line 422, in _open
'_open', req)
  File e:\software\python27\lib\urllib2.py, line 382, in _call_chain
result = func(*args)
  File e:\software\python27\lib\urllib2.py, line 1214, in http_open
return self.do_open(httplib.HTTPConnection, req)
  File e:\software\python27\lib\urllib2.py, line 1187, in do_open
r = h.getresponse(buffering=True)
  File e:\software\python27\lib\httplib.py, line 1045, in getresponse
response.begin()
  File e:\software\python27\lib\httplib.py, line 409, in begin
version, status, reason = self._read_status()
  File e:\software\python27\lib\httplib.py, line 373, in _read_status
raise BadStatusLine(line)

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] gae-python secure connection problem with ios since 07-04-2012

[f 1]

We have an problem with secure connection from iPhone and iPad
application since 07-04-2012. Three application platforms( iphone,
android and blackberry ) use the same web services. All of them work
properly but last friday all ios applications secure connections
failed. And users can not log in the iPhone and iPad application.
Blackberry and Android still working properly. There is no update on
ios system, iphone application and server side. Are there any changes
from appspot htttps connections? (Also appspot secure connections are
seen untrusted.). How can we handle this problem?

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-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] Re: App serving HTTP 500 out of nowhere

[Bernd F]

Just want to let you know that the app, including the new memcache
code, survived the first night.

On 3 Okt., 02:31, Stephen Johnson onepagewo...@gmail.com wrote:
 Not sure it will help any but hopefully you never know.







 On Sun, Oct 2, 2011 at 3:16 PM, Bernd F bernd.fi...@gmail.com wrote:
  Hi Stephen,

  yes I switched to threadsafe on Sept 12th, because of the new billing
  policy, but that issue already happened before.

  I'll change my code to use the low-level MemcacheService instead of
  JCache immediately. With JCache I tried both: saving the instance in a
  static variable for reuse and creating the cache object on every
  request. I can tell you that there is no difference (at least with
  JCache) in cpu usage and servlet execution time.

  Thank you very much for your suggestion!!

  On 2 Okt., 23:24, Stephen Johnson onepagewo...@gmail.com wrote:
   You don't mention if you have threadsafe on. If so, you might be
   experiencing some sort of deadlock or something with the way you are
   creating your JCache on every request. I'd try moving away from JCache
  and
   accessing the MemcacheService directly. I create a MemcacheService object
   for each thread and reuse that object. I've had no problems/issues like
   you've described but my QPS are probably not as much as yours. Here's
  some
   sample code

       private static ThreadLocalMemcacheService memcacheService =
   newThreadLocalMemcacheService() {

           protected synchronized MemcacheService initialValue() {

               return MemcacheServiceFactory.getMemcacheService();

           }

       };

       public static MemcacheService getService() {

          return memcacheService.get();

       }

   If you try switching to MemcacheService directly, please let us know if
  it
   helps or not.

   Stephen

   CortexConnect.com

   On Sun, Oct 2, 2011 at 1:58 PM, Bernd F bernd.fi...@gmail.com wrote:
Thank you for your input Jay, at least there is something I can cling
to. Could you be a little bit more specific about this bad value.

What could that be? Or better said: Is that anything I can control?

Btw: After I set the Max Idle value to Automatic a few days ago it
happened again (earlier today).

On 2 Okt., 20:27, Jay Young jayyoung9...@gmail.com wrote:
 It sounds like you have a bad value in memcache and when a servlet
  hits
it,
 it blocks the instance that's executing it.  When you have multiple
 instances running, other requests can be served by other instances.
   When
 you set it to 1, that one faulty instance gets backed up and requests
start
 timing out.  That's the only reason I can think of that clearing
  memcache
 AND changing your # of instances would solve the problem.  It's like
  your
 bad memcache value is a blockage in a stream.  Clearing memcache
  clears
the
 block.  Increasing the number of instances allows other requests to
  flow
 around the block.

--
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.

[google-appengine] Re: App serving HTTP 500 out of nowhere

[Bernd F]

I don't think this is related to M/R datastore spikes. The app has
been running stable since months and I'm suffering of this problems
since 3-4 weeks now.

FYI, I have also created an issue in the production tracker:
http://code.google.com/p/googleappengine/issues/detail?id=5790

- The whole app is down, even Servlets that doesn't use the datastore
respond with an HTTP 500 error

- When I do nothing the app recoveres itself after a few hours

- I once managed to fix it when I changed the Max Idle Instance
setting back to automatic. So this could be an hint that all my
instances were somehow blocked and app engine wasn't able to spin up
more instances.

- The usual fix is to clear all data from the memcache. If the
memcache is empty everything wents back to normal immediately. The
memcache is constantly filled with 12 items, each has a size 1MB. I
agree one could think it is an code issue, but as I said the whole app
is down, even Servlets that doesn't use Memcache/Datastor or vice
versa are not accessible. I've refactored my code 10 times already.

I don't know what to do anymore. All I get is move to HRD, but I
think I have to move away from App Engine. To make this clear: I will
move to HRD when the tool is released. Yeah I know there is a beta.
But anyway what has that todo with my problem? The whole app is down,
when the system status of M/R says okie dokie.





On 28 Sep., 22:51, Ikai Lan (Google) ika...@google.com wrote:
 Could these be related to datastore latency spikes? Those have been known to
 occur regularly on master/slave datastore, and we are encouraging developers
 to move to high replication. You can sign up for migration tool access here:

 https://docs.google.com/a/google.com/spreadsheet/viewform?authkey=CLX...

 --
 Ikai Lan
 Developer Programs Engineer, Google App Engine
 plus.ikailan.com | twitter.com/ikai







 On Tue, Sep 27, 2011 at 4:39 AM, Bernd F bernd.fi...@gmail.com wrote:
  Tonight it happened again, but after ~1 hour the app recovered on its
  own. There must be something wrong with app engine.

  On 20 Sep., 00:08, Bernd Final bernd.fi...@gmail.com wrote:
   I've had this issue for 5 or 6 times already. My app is running for a
   long time and I've had no problems so far, except this one:

   Out of nowhere, 20-30 seconds latency and only serving HTTP 500 errors
   for 99,9% of all requests. In most Servlets (yeah I'm using Java if
   that matters) I'm accessing the memcache, sometimes the datastore
   (Master/Slave). As you can imagine the app is totally unusable when
   this happens. When it occured the first time I didn't to any special,
   just waited for a couple of hours until the app recovered on it's own.

   Dashboard Milliseconds/Request Chart:
   Yesterday:http://bit.ly/pSF66E
   Last 30 Days:http://bit.ly/nYdZ2S

   When it happend again and again I tried to figure out what's going on,
   luckily I had some kind of Admin-Servlet deployed which allowed me to
   clear the entire memcache. Tried it, and voila, everything back to
   normal.

   - The memcache size was up to 1.3-1.5 MB in total (I did a rough
   estimation with the ByteArrayOutputStream trick). 12 Objects are
   stored in the memcache. Each Object is POJO which implements
   Serializable and contains some Strings, Integers and ArrayLists.
   - My first idea was to minimize the memory usage, because I though I
   was hitting the 1MB limit. At this time I didn't know the limit is for
   each object not for the whole cache, anyway I was able to reduce the
   size by 30-40% so the size is now about 800kb - 1MB
   - I'm running a cron job which cleans out garbage of the memcache.
   - This is how I access the memcache on every request:

  CacheManager.getInstance().getCacheFactory().createCache(Collections.emptyMap());
   - I'm using put and get Methods for storing / retrieving,
   - The key length is about 160 bytes

   Unfortunately I was not able to solve this issue yet, I would be very
   happy for ANY input.

  --
  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] Re: App serving HTTP 500 out of nowhere

[Bernd F]

Thank you for your input Jay, at least there is something I can cling
to. Could you be a little bit more specific about this bad value.

What could that be? Or better said: Is that anything I can control?

Btw: After I set the Max Idle value to Automatic a few days ago it
happened again (earlier today).


On 2 Okt., 20:27, Jay Young jayyoung9...@gmail.com wrote:
 It sounds like you have a bad value in memcache and when a servlet hits it,
 it blocks the instance that's executing it.  When you have multiple
 instances running, other requests can be served by other instances.  When
 you set it to 1, that one faulty instance gets backed up and requests start
 timing out.  That's the only reason I can think of that clearing memcache
 AND changing your # of instances would solve the problem.  It's like your
 bad memcache value is a blockage in a stream.  Clearing memcache clears the
 block.  Increasing the number of instances allows other requests to flow
 around the block.

-- 
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] Re: App serving HTTP 500 out of nowhere

[Bernd F]

Hi Stephen,

yes I switched to threadsafe on Sept 12th, because of the new billing
policy, but that issue already happened before.

I'll change my code to use the low-level MemcacheService instead of
JCache immediately. With JCache I tried both: saving the instance in a
static variable for reuse and creating the cache object on every
request. I can tell you that there is no difference (at least with
JCache) in cpu usage and servlet execution time.

Thank you very much for your suggestion!!



On 2 Okt., 23:24, Stephen Johnson onepagewo...@gmail.com wrote:
 You don't mention if you have threadsafe on. If so, you might be
 experiencing some sort of deadlock or something with the way you are
 creating your JCache on every request. I'd try moving away from JCache and
 accessing the MemcacheService directly. I create a MemcacheService object
 for each thread and reuse that object. I've had no problems/issues like
 you've described but my QPS are probably not as much as yours. Here's some
 sample code

     private static ThreadLocalMemcacheService memcacheService =
 newThreadLocalMemcacheService() {

         protected synchronized MemcacheService initialValue() {

             return MemcacheServiceFactory.getMemcacheService();

         }

     };

     public static MemcacheService getService() {

        return memcacheService.get();

     }

 If you try switching to MemcacheService directly, please let us know if it
 helps or not.

 Stephen

 CortexConnect.com







 On Sun, Oct 2, 2011 at 1:58 PM, Bernd F bernd.fi...@gmail.com wrote:
  Thank you for your input Jay, at least there is something I can cling
  to. Could you be a little bit more specific about this bad value.

  What could that be? Or better said: Is that anything I can control?

  Btw: After I set the Max Idle value to Automatic a few days ago it
  happened again (earlier today).

  On 2 Okt., 20:27, Jay Young jayyoung9...@gmail.com wrote:
   It sounds like you have a bad value in memcache and when a servlet hits
  it,
   it blocks the instance that's executing it.  When you have multiple
   instances running, other requests can be served by other instances.  When
   you set it to 1, that one faulty instance gets backed up and requests
  start
   timing out.  That's the only reason I can think of that clearing memcache
   AND changing your # of instances would solve the problem.  It's like your
   bad memcache value is a blockage in a stream.  Clearing memcache clears
  the
   block.  Increasing the number of instances allows other requests to flow
   around the block.

  --
  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] Re: App serving HTTP 500 out of nowhere

[Bernd F]

Tonight it happened again, but after ~1 hour the app recovered on its
own. There must be something wrong with app engine.



On 20 Sep., 00:08, Bernd Final bernd.fi...@gmail.com wrote:
 I've had this issue for 5 or 6 times already. My app is running for a
 long time and I've had no problems so far, except this one:

 Out of nowhere, 20-30 seconds latency and only serving HTTP 500 errors
 for 99,9% of all requests. In most Servlets (yeah I'm using Java if
 that matters) I'm accessing the memcache, sometimes the datastore
 (Master/Slave). As you can imagine the app is totally unusable when
 this happens. When it occured the first time I didn't to any special,
 just waited for a couple of hours until the app recovered on it's own.

 Dashboard Milliseconds/Request Chart:
 Yesterday:http://bit.ly/pSF66E
 Last 30 Days:http://bit.ly/nYdZ2S

 When it happend again and again I tried to figure out what's going on,
 luckily I had some kind of Admin-Servlet deployed which allowed me to
 clear the entire memcache. Tried it, and voila, everything back to
 normal.

 - The memcache size was up to 1.3-1.5 MB in total (I did a rough
 estimation with the ByteArrayOutputStream trick). 12 Objects are
 stored in the memcache. Each Object is POJO which implements
 Serializable and contains some Strings, Integers and ArrayLists.
 - My first idea was to minimize the memory usage, because I though I
 was hitting the 1MB limit. At this time I didn't know the limit is for
 each object not for the whole cache, anyway I was able to reduce the
 size by 30-40% so the size is now about 800kb - 1MB
 - I'm running a cron job which cleans out garbage of the memcache.
 - This is how I access the memcache on every request:
 CacheManager.getInstance().getCacheFactory().createCache(Collections.emptyMap());
 - I'm using put and get Methods for storing / retrieving,
 - The key length is about 160 bytes

 Unfortunately I was not able to solve this issue yet, I would be very
 happy for ANY input.

-- 
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.

[appengine-java] Local Datastore not working

[Josh F.]

All I did was delete my local_db.bin file and then clean the project
in eclipse.

Now I can't get my local Datastore to work...this  happens on a jsp
file
that works perfectly fine once deployed. The file was working fine
until I deleted local_db.bin and then it started throwing this error:

HTTP ERROR 500

Problem accessing /topics.jsp. Reason:

   Index: 0, Size: 0

Caused by:

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
   at java.util.ArrayList.RangeCheck(Unknown Source)
   at java.util.ArrayList.get(Unknown Source)
   at
org.datanucleus.store.appengine.query.LazyResult.get(LazyResult.java:
86)
   at
org.datanucleus.store.appengine.query.StreamingQueryResult.get(StreamingQueryResult.java:
107)
   at org.apache.jsp.topics_jsp._jspService(topics_jsp.java:107)
   at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:
377)
   at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:
313)
   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:
260)
   at
com.google.appengine.tools.development.PrivilegedJspServlet.access
$101(PrivilegedJspServlet.java:23)
   at com.google.appengine.tools.development.PrivilegedJspServlet
$2.run(PrivilegedJspServlet.java:59)
   at java.security.AccessController.doPrivileged(Native Method)
   at
com.google.appengine.tools.development.PrivilegedJspServlet.service(PrivilegedJspServlet.java:
57)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
511)
   at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1166)
   at
com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:
58)
   at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
   at
com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:
43)
   at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
   at
com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:
122)
   at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
   at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:
388)
   at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:
216)
   at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:
182)
   at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:
765)
   at
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
418)
   at
com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:
70)
   at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
152)
   at com.google.appengine.tools.development.JettyContainerService
$ApiProxyHandler.handle(JettyContainerService.java:351)
   at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
152)
   at org.mortbay.jetty.Server.handle(Server.java:326)
   at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
542)
   at org.mortbay.jetty.HttpConnection
$RequestHandler.headerComplete(HttpConnection.java:923)
   at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
   at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:
212)
   at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:
404)
   at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
409)
   at org.mortbay.thread.QueuedThreadPool
$PoolThread.run(QueuedThreadPool.java:582)

-- 
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: Local Datastore not working

[Josh F.]

This is really frustrating because I have to deploy everytime I want
to see a minor change. Someone please help, no matter what I do I
cannot get my local datastore back

On Apr 22, 10:56 am, Josh F. jef3...@gmail.com wrote:
 All I did was delete my local_db.bin file and then clean the project
 in eclipse.

 Now I can't get my local Datastore to work...this  happens on a jsp
 file
 that works perfectly fine once deployed. The file was working fine
 until I deleted local_db.bin and then it started throwing this error:

 HTTP ERROR 500

 Problem accessing /topics.jsp. Reason:

    Index: 0, Size: 0

 Caused by:

 java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
        at java.util.ArrayList.RangeCheck(Unknown Source)
        at java.util.ArrayList.get(Unknown Source)
        at
 org.datanucleus.store.appengine.query.LazyResult.get(LazyResult.java:
 86)
        at
 org.datanucleus.store.appengine.query.StreamingQueryResult.get(StreamingQueryResult.java:
 107)
        at org.apache.jsp.topics_jsp._jspService(topics_jsp.java:107)
        at
 org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:
 377)
        at
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:
 313)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:
 260)
        at
 com.google.appengine.tools.development.PrivilegedJspServlet.access
 $101(PrivilegedJspServlet.java:23)
        at com.google.appengine.tools.development.PrivilegedJspServlet
 $2.run(PrivilegedJspServlet.java:59)
        at java.security.AccessController.doPrivileged(Native Method)
        at
 com.google.appengine.tools.development.PrivilegedJspServlet.service(PrivilegedJspServlet.java:
 57)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
 511)
        at org.mortbay.jetty.servlet.ServletHandler
 $CachedChain.doFilter(ServletHandler.java:1166)
        at
 com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:
 58)
        at org.mortbay.jetty.servlet.ServletHandler
 $CachedChain.doFilter(ServletHandler.java:1157)
        at
 com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:
 43)
        at org.mortbay.jetty.servlet.ServletHandler
 $CachedChain.doFilter(ServletHandler.java:1157)
        at
 com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:
 122)
        at org.mortbay.jetty.servlet.ServletHandler
 $CachedChain.doFilter(ServletHandler.java:1157)
        at
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:
 388)
        at
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:
 216)
        at
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:
 182)
        at
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:
 765)
        at
 org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
 418)
        at
 com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:
 70)
        at
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
 152)
        at com.google.appengine.tools.development.JettyContainerService
 $ApiProxyHandler.handle(JettyContainerService.java:351)
        at
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
 152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
        at
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
 542)
        at org.mortbay.jetty.HttpConnection
 $RequestHandler.headerComplete(HttpConnection.java:923)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:
 212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:
 404)
        at
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
 409)
        at org.mortbay.thread.QueuedThreadPool
 $PoolThread.run(QueuedThreadPool.java:582)

-- 
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.

[google-appengine] Development Server Datastore issue

[Josh F.]

All I did was delete my local_db.bin file and then clean the project
in eclipse.

Now I can't get my Datastore to work...this  happens on a jsp file
that works perfectly fine once deployed. The file was working fine
until I deleted local_db.bin and then it started throwing this error:

HTTP ERROR 500

Problem accessing /topics.jsp. Reason:

Index: 0, Size: 0

Caused by:

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(Unknown Source)
at java.util.ArrayList.get(Unknown Source)
at
org.datanucleus.store.appengine.query.LazyResult.get(LazyResult.java:
86)
at
org.datanucleus.store.appengine.query.StreamingQueryResult.get(StreamingQueryResult.java:
107)
at org.apache.jsp.topics_jsp._jspService(topics_jsp.java:107)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:
377)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:
313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at com.google.appengine.tools.development.PrivilegedJspServlet.access
$101(PrivilegedJspServlet.java:23)
at com.google.appengine.tools.development.PrivilegedJspServlet
$2.run(PrivilegedJspServlet.java:59)
at java.security.AccessController.doPrivileged(Native Method)
at
com.google.appengine.tools.development.PrivilegedJspServlet.service(PrivilegedJspServlet.java:
57)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
511)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1166)
at
com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:
58)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
at
com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:
43)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
at
com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:
122)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:
388)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:
216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:
182)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:
765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
418)
at
com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:
70)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
152)
at com.google.appengine.tools.development.JettyContainerService
$ApiProxyHandler.handle(JettyContainerService.java:351)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
542)
at org.mortbay.jetty.HttpConnection
$RequestHandler.headerComplete(HttpConnection.java:923)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
409)
at org.mortbay.thread.QueuedThreadPool
$PoolThread.run(QueuedThreadPool.java:582)

-- 
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.

[appengine-java] Timeout when trying to upload to Blobstore (files 5k)

[Josh F.]

I'm trying to upload to the blobstore by programattically creating the POST 
request using the following class:

MultiPartFormOutputStreamhttp://svn.apache.org/repos/asf/wicket/branches/wicket-1.2.x/wicket-sandbox/src/jonathan/java/wicket/util/upload/MultiPartFormOutputStream.java

 BlobstoreService blobstoreService = 
BlobstoreServiceFactory.getBlobstoreService();
 try
 {
 uploadURL = 
blobstoreService.createUploadUrl(/upload);
 }
 catch(BlobstoreFailureException e)
 {
resp.sendRedirect(close.jsp);
 }
 
 //add host if in dev mode
 if(uploadURL.indexOf(http) == -1)
 {
 uploadURL = http://localhost:; + uploadURL;
 }
 URL url = new URL(uploadURL);
 // create a boundary string

 String boundary = MultiPartFormOutputStream.createBoundary();
 URLConnection urlConn = 
MultiPartFormOutputStream.createConnection(url); 
 urlConn.setReadTimeout(3);
 urlConn.setConnectTimeout(3);
 urlConn.setRequestProperty(Accept, */*);
 urlConn.setRequestProperty(Content-Type, 
MultiPartFormOutputStream.getContentType(boundary));
 urlConn.setRequestProperty(Cookie, name + = + value);
 // set some other request headers...
 urlConn.setRequestProperty(Connection, Keep-Alive);
 // no need to connect because getOutputStream() does it 

 MultiPartFormOutputStream out = null; 
try
{
 out = new MultiPartFormOutputStream(urlConn.getOutputStream(), 
boundary);
 // write a text field element
 out.writeField(old, oldBlobKey);
 out.writeField(topic, topic);
 out.writeField(category, category);
 out.writeField(key, key);
 // write bytes directly
 out.writeFile(myFile, text/html, content.html, htmlData);
 out.close();
}
catch(IOException e)
{
resp.sendRedirect(close.jsp);
}

Even when it times out  uploading and an exception gets thrown, the byte 
array still gets uploaded and the content.html file gets updated...I'm now 
sure how that works. I tried catching the exception with the above code, but 
sometimes it STILL displays an erro rmessage saying there was an uncaught 
IOException.

1.) Why is app-engine timing out when  uploading a file that is 5k in size?
2.) Why is it that even when I am attempting to catch the exception after 
creating the connection to the upload URL (in the case of the timeout), it 
still comes back as an uncaught exception...

Any help would be greatly appreciated! I really need to figure out why this 
Timeout is occurringI see people who talk about uploading files 
1MB...how is it that my tiny HTML files timeout when being uploaded to the 
Blobstore?
 

-- 
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] trying to import FileServiceFactory

[Josh F.]

I'm trying to do something like the code example for Writing file to 
Blobstore, however I can't seem to import the FileServiceFactory class.

http://code.google.com/appengine/docs/java/blobstore/overview.html#Writing_Files_to_the_Blobstore

The API documentation says it's under 
com.google.appengine.api.files.FileServiceFactory; but eclipse can't find 
it. 

-- 
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] Simulating POST Request to BLOBSTORE

[Josh F.]

Hello, I'm really at loss trying to track down the source of this
exception:

Apr 19, 2011 11:53:47 AM com.google.apphosting.utils.jetty.JettyLogger
warn
WARNING: /_ah/login
java.lang.NullPointerException
at
com.google.appengine.api.users.dev.LoginCookieUtils.encodeEmailAsUserId(LoginCookieUtils.java:
89)
at
com.google.appengine.api.users.dev.LoginCookieUtils.createCookie(LoginCookieUtils.java:
41)
at
com.google.appengine.api.users.dev.LocalLoginServlet.doPost(LocalLoginServlet.java:
90)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
511)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1166)
at
com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:
58)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
at
com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:
43)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
at
com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:
122)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:
388)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:
216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:
182)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:
765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
418)
at
com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:
70)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
152)
at com.google.appengine.tools.development.JettyContainerService
$ApiProxyHandler.handle(JettyContainerService.java:351)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
542)
at org.mortbay.jetty.HttpConnection
$RequestHandler.content(HttpConnection.java:938)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
409)
at org.mortbay.thread.QueuedThreadPool
$PoolThread.run(QueuedThreadPool.java:582)

This is occurring on my development server after running the app as a
Web Application through eclipse. The app basically stores .html files
in the blobstore, and allows the user to edit the html file through a
small jQuery based HTML editor.

I can retrieve the .html file contents from the blobstore using
fetchData to return a byte array of the contents. But once the user
has made changes to the html code via the editor, I'm trying to update
the entry in the DATASTORE that references the BlobKey string for the
corresponding .html file. So I am using a MultiPartFormOutputStream to
write directly to the request headers and simulate an HTTP POST
request.

Here is the code I have:

byte[] htmlData = content.getBytes();
for(int k=0; khtmlData.length; k++)
{
resp.getWriter().println(Byte  + k + :  + 
htmlData[k]);
}
BlobstoreService blobstoreService =
BlobstoreServiceFactory.getBlobstoreService();
String uploadURL = blobstoreService.createUploadUrl(/upload);

 //add host if in dev mode
 if(uploadURL.indexOf(http) == -1)
 {
 uploadURL = http://localhost:; + uploadURL;
 }
 URL url = new URL(uploadURL);
 // create a boundary string
 String boundary = MultiPartFormOutputStream.createBoundary();
 URLConnection urlConn =
MultiPartFormOutputStream.createConnection(url);
 urlConn.setReadTimeout(15000);
 urlConn.setRequestProperty(Accept, */*);
 urlConn.setRequestProperty(Content-Type,
MultiPartFormOutputStream.getContentType(boundary));
 // set some other request headers...
 urlConn.setRequestProperty(Connection, Keep-Alive);
 urlConn.setRequestProperty(Cache-Control, no-cache);
 // no need to connect because getOutputStream() does it
 

[appengine-java] Re: Simulating POST Request to BLOBSTORE

[Josh F.]

Solved. turns out I was not passing the cookie that keeps you logged
in.

Cookie [] cookies = req.getCookies();
String name = cookies[0].getName();
String value = cookies[0].getValue(); //this holds all
the information that the login servlet needs

to get the authentication cookie from the http request, then passed it
along to the final Upload servlet:

 urlConn.setRequestProperty(Cookie, name + = +
value);

It worked like a charm!!

On Apr 19, 12:03 pm, Josh F. jef3...@gmail.com wrote:
 Hello, I'm really at loss trying to track down the source of this
 exception:

 Apr 19, 2011 11:53:47 AM com.google.apphosting.utils.jetty.JettyLogger
 warn
 WARNING: /_ah/login
 java.lang.NullPointerException
         at
 com.google.appengine.api.users.dev.LoginCookieUtils.encodeEmailAsUserId(LoginCookieUtils.java:
 89)
         at
 com.google.appengine.api.users.dev.LoginCookieUtils.createCookie(LoginCookieUtils.java:
 41)
         at
 com.google.appengine.api.users.dev.LocalLoginServlet.doPost(LocalLoginServlet.java:
 90)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
 511)
         at org.mortbay.jetty.servlet.ServletHandler
 $CachedChain.doFilter(ServletHandler.java:1166)
         at
 com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:
 58)
         at org.mortbay.jetty.servlet.ServletHandler
 $CachedChain.doFilter(ServletHandler.java:1157)
         at
 com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:
 43)
         at org.mortbay.jetty.servlet.ServletHandler
 $CachedChain.doFilter(ServletHandler.java:1157)
         at
 com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:
 122)
         at org.mortbay.jetty.servlet.ServletHandler
 $CachedChain.doFilter(ServletHandler.java:1157)
         at
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:
 388)
         at
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:
 216)
         at
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:
 182)
         at
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:
 765)
         at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
 418)
         at
 com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:
 70)
         at
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
 152)
         at com.google.appengine.tools.development.JettyContainerService
 $ApiProxyHandler.handle(JettyContainerService.java:351)
         at
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:
 152)
         at org.mortbay.jetty.Server.handle(Server.java:326)
         at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
 542)
         at org.mortbay.jetty.HttpConnection
 $RequestHandler.content(HttpConnection.java:938)
         at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
         at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
         at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
         at
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
 409)
         at org.mortbay.thread.QueuedThreadPool
 $PoolThread.run(QueuedThreadPool.java:582)

 This is occurring on my development server after running the app as a
 Web Application through eclipse. The app basically stores .html files
 in the blobstore, and allows the user to edit the html file through a
 small jQuery based HTML editor.

 I can retrieve the .html file contents from the blobstore using
 fetchData to return a byte array of the contents. But once the user
 has made changes to the html code via the editor, I'm trying to update
 the entry in the DATASTORE that references the BlobKey string for the
 corresponding .html file. So I am using a MultiPartFormOutputStream to
 write directly to the request headers and simulate an HTTP POST
 request.

 Here is the code I have:

 byte[] htmlData = content.getBytes();
                 for(int k=0; khtmlData.length; k++)
                 {
                         resp.getWriter().println(Byte  + k + :  + 
 htmlData[k]);
                 }
                 BlobstoreService blobstoreService =
 BlobstoreServiceFactory.getBlobstoreService();
                 String uploadURL = 
 blobstoreService.createUploadUrl(/upload);

                              //add host if in dev mode
                  if(uploadURL.indexOf(http) == -1)
                  {
                          uploadURL = http://localhost:; + uploadURL;
                  }
                  URL url = new URL(uploadURL);
                  // create a boundary string

Re: [google-appengine] Helloworld Tutorial - Segmentation Fault

[Will F]

I examined the verbose output and noted the bottommost line was 

import _hashlib # dynamically loaded from 
/usr/local/lib/python2.5/lib-dynload/_hashlib.so

So I ran a couple more tests, and when I ran Python 2.5 interactively and 
tried to import the _hashlib module, it worked, there were no errors.

I also went to this blog: 
http://www.learningtechnicalstuff.com/2010/10/installing-python-google-appengine-sdk.html
 and 
tried his approach. This did not work either.

-- 
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] Helloworld Tutorial - Segmentation Fault

[Will F]

I am just starting to use google app engine and have just started
running the tutorial. When I do this:

$ python2.5 google_appengine/dev_appserver.py helloworld/

it says 'Segmentation Fault'.

I am running Ubuntu 10.10. I installed Python 2.5 from the site with
help from this site: 
http://thedarren.blogspot.com/2010/11/install-appengine-python-sdk-on-ubuntu.html.
The reason I have python2.5 at the beginning of my command is that I
did an altinstall of Python 2.5 so that I would still be able to use
Python 2.7.

Everything looks like it should work but it isn't. Does anyone know
what my issue is?

-- 
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] Helloworld Tutorial - Segmentation Fault

[Will F]

So I am able to run Python 2.5 interactively. It is only when I run 
dev_appserver.py that I get a seg fault. I did more tests and even when I 
just run:

$ ./google_appengine/dev_appserver.py

it gives me a seg fault. I don't know if this helps, but I thought it might.

-- 
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] Helloworld Tutorial - Segmentation Fault

[Will F]

So I did as you suggested, I ran it with the verbose output:

# installing zipimport hook
import zipimport # builtin
# installed zipimport hook
# /usr/local/lib/python2.5/site.pyc matches /usr/local/lib/python2.5/site.py
import site # precompiled from /usr/local/lib/python2.5/site.pyc
# /usr/local/lib/python2.5/os.pyc matches /usr/local/lib/python2.5/os.py
import os # precompiled from /usr/local/lib/python2.5/os.pyc
import errno # builtin
import posix # builtin
# /usr/local/lib/python2.5/posixpath.pyc matches 
/usr/local/lib/python2.5/posixpath.py
import posixpath # precompiled from /usr/local/lib/python2.5/posixpath.pyc
# /usr/local/lib/python2.5/stat.pyc matches /usr/local/lib/python2.5/stat.py
import stat # precompiled from /usr/local/lib/python2.5/stat.pyc
# /usr/local/lib/python2.5/UserDict.pyc matches 
/usr/local/lib/python2.5/UserDict.py
import UserDict # precompiled from /usr/local/lib/python2.5/UserDict.pyc
# /usr/local/lib/python2.5/copy_reg.pyc matches 
/usr/local/lib/python2.5/copy_reg.py
import copy_reg # precompiled from /usr/local/lib/python2.5/copy_reg.pyc
# /usr/local/lib/python2.5/types.pyc matches 
/usr/local/lib/python2.5/types.py
import types # precompiled from /usr/local/lib/python2.5/types.pyc
import _types # builtin
# /usr/local/lib/python2.5/warnings.pyc matches 
/usr/local/lib/python2.5/warnings.py
import warnings # precompiled from /usr/local/lib/python2.5/warnings.pyc
# /usr/local/lib/python2.5/linecache.pyc matches 
/usr/local/lib/python2.5/linecache.py
import linecache # precompiled from /usr/local/lib/python2.5/linecache.pyc
import encodings # directory /usr/local/lib/python2.5/encodings
# /usr/local/lib/python2.5/encodings/__init__.pyc matches 
/usr/local/lib/python2.5/encodings/__init__.py
import encodings # precompiled from 
/usr/local/lib/python2.5/encodings/__init__.pyc
# /usr/local/lib/python2.5/codecs.pyc matches 
/usr/local/lib/python2.5/codecs.py
import codecs # precompiled from /usr/local/lib/python2.5/codecs.pyc
import _codecs # builtin
# /usr/local/lib/python2.5/encodings/aliases.pyc matches 
/usr/local/lib/python2.5/encodings/aliases.py
import encodings.aliases # precompiled from 
/usr/local/lib/python2.5/encodings/aliases.pyc
# /usr/local/lib/python2.5/encodings/utf_8.pyc matches 
/usr/local/lib/python2.5/encodings/utf_8.py
import encodings.utf_8 # precompiled from 
/usr/local/lib/python2.5/encodings/utf_8.pyc
Python 2.5.5 (r255:77872, Feb 17 2011, 21:03:23) 
[GCC 4.4.5] on linux2
Type help, copyright, credits or license for more information.
import google # directory 
/home/admin/google_app_engine/google_appengine/google
# /home/admin/google_app_engine/google_appengine/google/__init__.pyc matches 
/home/admin/google_app_engine/google_appengine/google/__init__.py
import google # precompiled from 
/home/admin/google_app_engine/google_appengine/google/__init__.pyc
import google.appengine # directory 
/home/admin/google_app_engine/google_appengine/google/appengine
# 
/home/admin/google_app_engine/google_appengine/google/appengine/__init__.pyc 
matches 
/home/admin/google_app_engine/google_appengine/google/appengine/__init__.py
import google.appengine # precompiled from 
/home/admin/google_app_engine/google_appengine/google/appengine/__init__.pyc
import google.appengine.tools # directory 
/home/admin/google_app_engine/google_appengine/google/appengine/tools
# 
/home/admin/google_app_engine/google_appengine/google/appengine/tools/__init__.pyc
 
matches 
/home/admin/google_app_engine/google_appengine/google/appengine/tools/__init__.py
import google.appengine.tools # precompiled from 
/home/admin/google_app_engine/google_appengine/google/appengine/tools/__init__.pyc
# 
/home/admin/google_app_engine/google_appengine/google/appengine/tools/os_compat.pyc
 
matches 
/home/admin/google_app_engine/google_appengine/google/appengine/tools/os_compat.py
import google.appengine.tools.os_compat # precompiled from 
/home/admin/google_app_engine/google_appengine/google/appengine/tools/os_compat.pyc
dlopen(/usr/local/lib/python2.5/lib-dynload/time.so, 2);
import time # dynamically loaded from 
/usr/local/lib/python2.5/lib-dynload/time.so
# /usr/local/lib/python2.5/getopt.pyc matches 
/usr/local/lib/python2.5/getopt.py
import getopt # precompiled from /usr/local/lib/python2.5/getopt.pyc
import logging # directory /usr/local/lib/python2.5/logging
# /usr/local/lib/python2.5/logging/__init__.pyc matches 
/usr/local/lib/python2.5/logging/__init__.py
import logging # precompiled from 
/usr/local/lib/python2.5/logging/__init__.pyc
# /usr/local/lib/python2.5/string.pyc matches 
/usr/local/lib/python2.5/string.py
import string # precompiled from /usr/local/lib/python2.5/string.pyc
# /usr/local/lib/python2.5/re.pyc matches /usr/local/lib/python2.5/re.py
import re # precompiled from /usr/local/lib/python2.5/re.pyc
# /usr/local/lib/python2.5/sre_compile.pyc matches 
/usr/local/lib/python2.5/sre_compile.py
import sre_compile # precompiled from 
/usr/local/lib/python2.5/sre_compile.pyc
import 

[appengine-java] Unable to update

[f...@ncky]

Hello,
I try do deploy with eclipse and i have that message:

Unable to update:
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source)
at com.sun.net.ssl.internal.ssl.BaseSSLSocketImpl.connect(Unknown
Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.init(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown
Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
Source)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown
Source)
at
sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown
Source)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown
Source)
at
com.google.appengine.tools.admin.ServerConnection.connect(ServerConnection.java:
337)
at
com.google.appengine.tools.admin.ServerConnection.send(ServerConnection.java:
133)
at
com.google.appengine.tools.admin.ServerConnection.post(ServerConnection.java:
82)
at
com.google.appengine.tools.admin.AppVersionUpload.send(AppVersionUpload.java:
582)
at
com.google.appengine.tools.admin.AppVersionUpload.beginTransaction(AppVersionUpload.java:
400)
at
com.google.appengine.tools.admin.AppVersionUpload.doUpload(AppVersionUpload.java:
112)
at
com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:
56)
at
com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngineBridgeImpl.java:
271)
at
com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(DeployProjectJob.java:
145)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:
38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


Any Ideas are welcome

-- 
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.

[google-appengine] gae app cannot be displayed in my account

[f...@wqfw.de]

I used my google apps account(e.g. a...@wqfw.de, means custom domian,
doesn't '@gmail.com') to create a new gae, and that has successed.

But, I opened https://appengine.google.com again. The browser still
switch to https://appengine.google.com/start.

I created another gae again(in Create an Application page, that tell
me You have 9 applications remaining.), then back to 
https://appengine.google.com,
the browser is gone to https://appengine.google.com/start again :(.

What's wrong?



Br,
Fisher.

-- 
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.