[google-appengine] Re: Google Places API wrapper for Java GAE

[Richard Watson]

This guy claims to have a first draft of one:
http://code.google.com/p/google-places-api-client/ 

This guy says use the standard Google Java api, with examples:
http://ddewaele.blogspot.com/2011/05/introducing-google-places-api.html 

On Wednesday, August 29, 2012 10:03:35 PM UTC+2, Rahul Tongia wrote:
>
> Hi There,
>
> I want to use google places API from the service side at my Java appengine 
> and GWT app. It is possible using URLFetch on places web services. Is there 
> anyone who has written a library which converts the JSON response to Java 
> objects.
>
> This would save me considerable time in case some one has done that.
>
> Thanks a lot
>
> Rahul
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/CLNppYZOFCYJ.
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] Re: Weird Instance Scheduler

[Carl Schroeder]

Try making a page that consists of more than a single request to the 
server. A burst of requests that is served (not static content) under the 
pending latency time would usually trigger an instance spin-up. 
Now that spin-up times are back to normal, I am not seeing this behavior 
nearly as often.


On Wednesday, August 29, 2012 6:07:30 PM UTC-7, Takashi Matsuo (Google) 
wrote:
>
>
> Jeff,
>
> Thanks for the suggestion, and probably that's true. I've chosen this test 
> from Mos's e-mail, because I got a feeling that he saw odd behaviors even 
> with one request per minute. Hopefully I can do another test based on your 
> suggestion soon.
>
> Please note that you can also provide your test result on our issue 
> tracker and help us reproduce the issue :)
>
> Thanks,
>
>
> On Thu, Aug 30, 2012 at 9:16 AM, Jeff Schnitzer 
> 
> > wrote:
>
>> This is not a very good test.  Better would be:  Run 'ab -c 1' against it 
>> and see if you get any cold starts.  Change 1 to a larger number, up to 
>> what concurrency we should expect for a multithreaded instance.
>>
>> Jeff
>>
>>
>> On Wed, Aug 29, 2012 at 6:54 PM, Takashi Matsuo 
>> 
>> > wrote:
>>
>>>
>>> Hi Mos and everyone,
>>>
>>> I'm trying to reproduce the issue about min idle instance which some of 
>>> you guys reported here in this thread, saying "Setting min idle instances 
>>> doesn't work for me".
>>>
>>> My initial test is just with a simple helloworld Java application 
>>> multithread enabled, setting 1 min idle instance, and setting 1 min cron 
>>> job. I ran this test for about 2 and half days. I think it just worked as 
>>> expected. The resident instance had been alive and handled 3625 requests 
>>> during the test.
>>>
>>> What I'm planning to do next is another experiment with an application 
>>> with Spring MVC. I'll update with the result hopefully next week.
>>>
>>> At the same time, I'd like one of you to file an issue on our issue 
>>> tracker for this particular topic, 'Setting min idle instances doesn't 
>>> work', hopefully with expected behavior, actual results, a characteristic 
>>> of the application like average time for loading requests as well as normal 
>>> requests, etc. I've done a quick search on our issue tracker, and I don't 
>>> think there's any issue yet. If there's already an issue about it, please 
>>> let me know.
>>>
>>> Thanks,
>>>
>>>
>>> On Tue, Aug 28, 2012 at 2:13 AM, Carl Schroeder 
>>> 
>>> > wrote:
>>>
 Yep. Googlites, let us know what else you need to run this down.


 On Monday, August 27, 2012 10:05:41 AM UTC-7, Mos wrote:

> In http://code.google.com/p/**googleappengine/issues/detail?**
> id=8004#c8
>   
> I described in detail a current example of the nonconforming 
> instance-handling of GAE.
> Please check the comment, the screenshot and the log-file I filed 
> there.
>
> Dear GAE-Team, what else do you need to fix this?  In this thread and 
> in several issues you should have more than enough proof and examples.
>
> Cheers
> Mos
>
> On Mon, Aug 27, 2012 at 5:34 PM, Mos  wrote:
>
>>  I saw the same behavior (as discussed before in the thread). Many 
>> other people reported this again and again on this mailing-list.
>> Google has to acknowledge that the current implementation is buggy or 
>> the implementation works but doesn't make any sense in practice.  
>>
>> Bye the way - The problem is not restricted to resident instances. 
>> From time to time the same happens for dynamic instances:
>>
>> One or more dynamic instances are running and are almost idle  
>> (sometimes really idle==no request or just one request is served). 
>> Request comes and starts a new dynamic instance, it goes through 
>> 30-40 seconds of warmup, then request is served.
>>
>>
>> On Mon, Aug 27, 2012 at 5:19 PM, Carl D'Halluin 
>> wrote:
>>
>>> Hi Carl,
>>>
>>> I see exactly the same behaviour for my Java appengine app.
>>> Resident instance does nothing; instead idle instance is started, 
>>> going through several seconds of warmup, then request is served.
>>>
>>> Regards
>>>
>>>
>>> On Mon, Aug 27, 2012 at 5:11 PM, Carl Schroeder <
>>> schroede...@gmail.com> wrote:
>>>
 2012-08-27 08:05 is the point in the logs. 1 Resident instance. No 
 Dynamic instances. 
 The request was sent to a cold starting Dynamic instance. Resident 
 instance did nothing. 
 Request took 18 seconds to serve.


 On Monday, August 27, 2012 2:16:25 AM UTC-7, Johan Euphrosine 
 (Google) wrote:

> On Mon, Aug 27, 2012 at 5:59 AM, Carl Schroeder 
>  wrote: 
> > Let me see if I understand this correctly: there is currently no 
> way on app 
> > engine to ensure that ther

Re: [google-appengine] Re: Weird Instance Scheduler

[Jeff Schnitzer]

I really do wish I had time right now to help track this down - believe me,
this issue is very relevant to my interests!

Jeff

On Wed, Aug 29, 2012 at 9:07 PM, Takashi Matsuo  wrote:

>
> Jeff,
>
> Thanks for the suggestion, and probably that's true. I've chosen this test
> from Mos's e-mail, because I got a feeling that he saw odd behaviors even
> with one request per minute. Hopefully I can do another test based on your
> suggestion soon.
>
> Please note that you can also provide your test result on our issue
> tracker and help us reproduce the issue :)
>
> Thanks,
>
>
> On Thu, Aug 30, 2012 at 9:16 AM, Jeff Schnitzer wrote:
>
>> This is not a very good test.  Better would be:  Run 'ab -c 1' against it
>> and see if you get any cold starts.  Change 1 to a larger number, up to
>> what concurrency we should expect for a multithreaded instance.
>>
>> Jeff
>>
>>
>> On Wed, Aug 29, 2012 at 6:54 PM, Takashi Matsuo wrote:
>>
>>>
>>> Hi Mos and everyone,
>>>
>>> I'm trying to reproduce the issue about min idle instance which some of
>>> you guys reported here in this thread, saying "Setting min idle instances
>>> doesn't work for me".
>>>
>>> My initial test is just with a simple helloworld Java application
>>> multithread enabled, setting 1 min idle instance, and setting 1 min cron
>>> job. I ran this test for about 2 and half days. I think it just worked as
>>> expected. The resident instance had been alive and handled 3625 requests
>>> during the test.
>>>
>>> What I'm planning to do next is another experiment with an application
>>> with Spring MVC. I'll update with the result hopefully next week.
>>>
>>> At the same time, I'd like one of you to file an issue on our issue
>>> tracker for this particular topic, 'Setting min idle instances doesn't
>>> work', hopefully with expected behavior, actual results, a characteristic
>>> of the application like average time for loading requests as well as normal
>>> requests, etc. I've done a quick search on our issue tracker, and I don't
>>> think there's any issue yet. If there's already an issue about it, please
>>> let me know.
>>>
>>> Thanks,
>>>
>>>
>>> On Tue, Aug 28, 2012 at 2:13 AM, Carl Schroeder <
>>> schroeder.car...@gmail.com> wrote:
>>>
 Yep. Googlites, let us know what else you need to run this down.


 On Monday, August 27, 2012 10:05:41 AM UTC-7, Mos wrote:

> In http://code.google.com/p/**googleappengine/issues/detail?**
> id=8004#c8
> I described in detail a current example of the nonconforming
> instance-handling of GAE.
> Please check the comment, the screenshot and the log-file I filed
> there.
>
> Dear GAE-Team, what else do you need to fix this?  In this thread and
> in several issues you should have more than enough proof and examples.
>
> Cheers
> Mos
>
> On Mon, Aug 27, 2012 at 5:34 PM, Mos  wrote:
>
>>  I saw the same behavior (as discussed before in the thread). Many
>> other people reported this again and again on this mailing-list.
>> Google has to acknowledge that the current implementation is buggy or
>> the implementation works but doesn't make any sense in practice.
>>
>> Bye the way - The problem is not restricted to resident instances.
>> From time to time the same happens for dynamic instances:
>>
>> One or more dynamic instances are running and are almost idle
>> (sometimes really idle==no request or just one request is served).
>> Request comes and starts a new dynamic instance, it goes through
>> 30-40 seconds of warmup, then request is served.
>>
>>
>> On Mon, Aug 27, 2012 at 5:19 PM, Carl D'Halluin 
>> wrote:
>>
>>> Hi Carl,
>>>
>>> I see exactly the same behaviour for my Java appengine app.
>>> Resident instance does nothing; instead idle instance is started,
>>> going through several seconds of warmup, then request is served.
>>>
>>> Regards
>>>
>>>
>>> On Mon, Aug 27, 2012 at 5:11 PM, Carl Schroeder <
>>> schroede...@gmail.com> wrote:
>>>
 2012-08-27 08:05 is the point in the logs. 1 Resident instance. No
 Dynamic instances.
 The request was sent to a cold starting Dynamic instance. Resident
 instance did nothing.
 Request took 18 seconds to serve.


 On Monday, August 27, 2012 2:16:25 AM UTC-7, Johan Euphrosine
 (Google) wrote:

> On Mon, Aug 27, 2012 at 5:59 AM, Carl Schroeder
>  wrote:
> > Let me see if I understand this correctly: there is currently no
> way on app
> > engine to ensure that there is an instance ready to process
> incoming
> > requests for an app that has been idle for some period of time.
> Min idle
> > instances (labeled as Resident) sit there and do almost nothing
> while user
>

Re: [google-appengine] Re: Weird Instance Scheduler

[Takashi Matsuo]

Jeff,

Thanks for the suggestion, and probably that's true. I've chosen this test
from Mos's e-mail, because I got a feeling that he saw odd behaviors even
with one request per minute. Hopefully I can do another test based on your
suggestion soon.

Please note that you can also provide your test result on our issue tracker
and help us reproduce the issue :)

Thanks,


On Thu, Aug 30, 2012 at 9:16 AM, Jeff Schnitzer  wrote:

> This is not a very good test.  Better would be:  Run 'ab -c 1' against it
> and see if you get any cold starts.  Change 1 to a larger number, up to
> what concurrency we should expect for a multithreaded instance.
>
> Jeff
>
>
> On Wed, Aug 29, 2012 at 6:54 PM, Takashi Matsuo wrote:
>
>>
>> Hi Mos and everyone,
>>
>> I'm trying to reproduce the issue about min idle instance which some of
>> you guys reported here in this thread, saying "Setting min idle instances
>> doesn't work for me".
>>
>> My initial test is just with a simple helloworld Java application
>> multithread enabled, setting 1 min idle instance, and setting 1 min cron
>> job. I ran this test for about 2 and half days. I think it just worked as
>> expected. The resident instance had been alive and handled 3625 requests
>> during the test.
>>
>> What I'm planning to do next is another experiment with an application
>> with Spring MVC. I'll update with the result hopefully next week.
>>
>> At the same time, I'd like one of you to file an issue on our issue
>> tracker for this particular topic, 'Setting min idle instances doesn't
>> work', hopefully with expected behavior, actual results, a characteristic
>> of the application like average time for loading requests as well as normal
>> requests, etc. I've done a quick search on our issue tracker, and I don't
>> think there's any issue yet. If there's already an issue about it, please
>> let me know.
>>
>> Thanks,
>>
>>
>> On Tue, Aug 28, 2012 at 2:13 AM, Carl Schroeder <
>> schroeder.car...@gmail.com> wrote:
>>
>>> Yep. Googlites, let us know what else you need to run this down.
>>>
>>>
>>> On Monday, August 27, 2012 10:05:41 AM UTC-7, Mos wrote:
>>>
 In http://code.google.com/p/**googleappengine/issues/detail?**
 id=8004#c8
 I described in detail a current example of the nonconforming
 instance-handling of GAE.
 Please check the comment, the screenshot and the log-file I filed there.

 Dear GAE-Team, what else do you need to fix this?  In this thread and
 in several issues you should have more than enough proof and examples.

 Cheers
 Mos

 On Mon, Aug 27, 2012 at 5:34 PM, Mos  wrote:

>  I saw the same behavior (as discussed before in the thread). Many
> other people reported this again and again on this mailing-list.
> Google has to acknowledge that the current implementation is buggy or
> the implementation works but doesn't make any sense in practice.
>
> Bye the way - The problem is not restricted to resident instances.
> From time to time the same happens for dynamic instances:
>
> One or more dynamic instances are running and are almost idle
> (sometimes really idle==no request or just one request is served).
> Request comes and starts a new dynamic instance, it goes through 30-40
> seconds of warmup, then request is served.
>
>
> On Mon, Aug 27, 2012 at 5:19 PM, Carl D'Halluin wrote:
>
>> Hi Carl,
>>
>> I see exactly the same behaviour for my Java appengine app.
>> Resident instance does nothing; instead idle instance is started,
>> going through several seconds of warmup, then request is served.
>>
>> Regards
>>
>>
>> On Mon, Aug 27, 2012 at 5:11 PM, Carl Schroeder <
>> schroede...@gmail.com> wrote:
>>
>>> 2012-08-27 08:05 is the point in the logs. 1 Resident instance. No
>>> Dynamic instances.
>>> The request was sent to a cold starting Dynamic instance. Resident
>>> instance did nothing.
>>> Request took 18 seconds to serve.
>>>
>>>
>>> On Monday, August 27, 2012 2:16:25 AM UTC-7, Johan Euphrosine
>>> (Google) wrote:
>>>
 On Mon, Aug 27, 2012 at 5:59 AM, Carl Schroeder
  wrote:
 > Let me see if I understand this correctly: there is currently no
 way on app
 > engine to ensure that there is an instance ready to process
 incoming
 > requests for an app that has been idle for some period of time.
 Min idle
 > instances (labeled as Resident) sit there and do almost nothing
 while user
 > facing requests are instead sent to cold instance starts. If
 true, that
 > dovetails with what I have seen in the behavior of my app. For
 python
 > runtimes with sub-second spinup times, this is no big deal. For
 java
 > runtimes with spinup times in double digit seconds it

Re: [google-appengine] Re: Weird Instance Scheduler

[Jeff Schnitzer]

This is not a very good test.  Better would be:  Run 'ab -c 1' against it
and see if you get any cold starts.  Change 1 to a larger number, up to
what concurrency we should expect for a multithreaded instance.

Jeff

On Wed, Aug 29, 2012 at 6:54 PM, Takashi Matsuo  wrote:

>
> Hi Mos and everyone,
>
> I'm trying to reproduce the issue about min idle instance which some of
> you guys reported here in this thread, saying "Setting min idle instances
> doesn't work for me".
>
> My initial test is just with a simple helloworld Java application
> multithread enabled, setting 1 min idle instance, and setting 1 min cron
> job. I ran this test for about 2 and half days. I think it just worked as
> expected. The resident instance had been alive and handled 3625 requests
> during the test.
>
> What I'm planning to do next is another experiment with an application
> with Spring MVC. I'll update with the result hopefully next week.
>
> At the same time, I'd like one of you to file an issue on our issue
> tracker for this particular topic, 'Setting min idle instances doesn't
> work', hopefully with expected behavior, actual results, a characteristic
> of the application like average time for loading requests as well as normal
> requests, etc. I've done a quick search on our issue tracker, and I don't
> think there's any issue yet. If there's already an issue about it, please
> let me know.
>
> Thanks,
>
>
> On Tue, Aug 28, 2012 at 2:13 AM, Carl Schroeder <
> schroeder.car...@gmail.com> wrote:
>
>> Yep. Googlites, let us know what else you need to run this down.
>>
>>
>> On Monday, August 27, 2012 10:05:41 AM UTC-7, Mos wrote:
>>
>>> In 
>>> http://code.google.com/p/**googleappengine/issues/detail?**id=8004#c8
>>> I described in detail a current example of the nonconforming
>>> instance-handling of GAE.
>>> Please check the comment, the screenshot and the log-file I filed there.
>>>
>>> Dear GAE-Team, what else do you need to fix this?  In this thread and in
>>> several issues you should have more than enough proof and examples.
>>>
>>> Cheers
>>> Mos
>>>
>>> On Mon, Aug 27, 2012 at 5:34 PM, Mos  wrote:
>>>
  I saw the same behavior (as discussed before in the thread). Many
 other people reported this again and again on this mailing-list.
 Google has to acknowledge that the current implementation is buggy or
 the implementation works but doesn't make any sense in practice.

 Bye the way - The problem is not restricted to resident instances. From
 time to time the same happens for dynamic instances:

 One or more dynamic instances are running and are almost idle
 (sometimes really idle==no request or just one request is served).
 Request comes and starts a new dynamic instance, it goes through 30-40
 seconds of warmup, then request is served.


 On Mon, Aug 27, 2012 at 5:19 PM, Carl D'Halluin wrote:

> Hi Carl,
>
> I see exactly the same behaviour for my Java appengine app.
> Resident instance does nothing; instead idle instance is started,
> going through several seconds of warmup, then request is served.
>
> Regards
>
>
> On Mon, Aug 27, 2012 at 5:11 PM, Carl Schroeder  > wrote:
>
>> 2012-08-27 08:05 is the point in the logs. 1 Resident instance. No
>> Dynamic instances.
>> The request was sent to a cold starting Dynamic instance. Resident
>> instance did nothing.
>> Request took 18 seconds to serve.
>>
>>
>> On Monday, August 27, 2012 2:16:25 AM UTC-7, Johan Euphrosine
>> (Google) wrote:
>>
>>> On Mon, Aug 27, 2012 at 5:59 AM, Carl Schroeder
>>>  wrote:
>>> > Let me see if I understand this correctly: there is currently no
>>> way on app
>>> > engine to ensure that there is an instance ready to process
>>> incoming
>>> > requests for an app that has been idle for some period of time.
>>> Min idle
>>> > instances (labeled as Resident) sit there and do almost nothing
>>> while user
>>> > facing requests are instead sent to cold instance starts. If true,
>>> that
>>> > dovetails with what I have seen in the behavior of my app. For
>>> python
>>> > runtimes with sub-second spinup times, this is no big deal. For
>>> java
>>> > runtimes with spinup times in double digit seconds it is a
>>> deal-breaker of a
>>> > "feature".
>>> >
>>> > The problem seems to be that the scheduler thinks sending a
>>> request to a
>>> > non-existent dynamic instance is a better idea than using the
>>> Resident
>>> > instance for it's intended purpose: to serve requests when dynamic
>>> instances
>>> > are unable to. This is probably a corner case born of low traffic
>>> conditions
>>> > that allow user request serving dynamic instances to despawn.
>>>
>>> Hi Carl,
>>>
>>> That's not what we obser

Re: [google-appengine] Python 2.7 and SQLite on Windows 7: unable to open database file

[Bryce Cutt]

Hi Robert,

I have been digging into it a bit more and I know what is happening, I just 
don't know why it is happening. I have a temporary solution that does not 
require running as administrator. I detailed all this on the issue page so 
it is all in one place.

- Bryce


On Tuesday, August 28, 2012 10:59:44 PM UTC-7, Robert Fischer wrote:
>
> What I mean to say is I gave up on a proper "fix" so that I could work, 
> but would love find out why it's not working when it's running as the same 
> user who owns and also has permission to the database.
>
> -Robert Fischer
> www.DealScorcher.com
>
>
>
> On Tue, Aug 28, 2012 at 10:54 PM, Robert Fischer 
> 
> > wrote:
>
>> I know this probably isn't what you're looking to hear but I had the same 
>> problem and was able to "solve" it by running the dev server as 
>> administrator.
>>
>> Another benefit to this is being able to run on :80.
>>
>> I'd love to hear about a better solution though...
>>
>> -Robert Fischer
>> www.DealScorcher.com
>>
>>
>>
>> On Tue, Aug 28, 2012 at 10:31 PM, Bryce Cutt 
>> > wrote:
>>
>>> I am having an odd issue with Python 2.7 and SQLite and am wondering if 
>>> anyone has seen it or has some insight.
>>>
>>> I recently decided to try porting some of my Python apps to the python27 
>>> runtime and the first step was to install Python 2.7 on my dev machine 
>>> (Windows 7 64bit). Now whenever I run an app with --use_sqlite I get the 
>>> exception "InternalError: unable to open database file" as soon as I 
>>> try to write an entity to the datastore. I have traced this back to sqlite 
>>> being unable to write some temp files to my "C:\Windows" folder (see issue 
>>> linked below).
>>>
>>> I have tried to detail as much as possible in my response to this issue:
>>> http://code.google.com/p/googleappengine/issues/detail?id=7717
>>>
>>> I am a bit stumped on what to do next. For now I have gone back to 
>>> developing with Python 2.6 but that is not really a solution.
>>>
>>> - Bryce
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msg/google-appengine/-/2CCuwzuo5WYJ.
>>> To post to this group, send email to 
>>> google-a...@googlegroups.com
>>> .
>>> To unsubscribe from this group, send email to 
>>> google-appengi...@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 view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/gcFiaQoJ6A4J.
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] Search API Unit Tests

[Jason Galea]

removing all the documents at teardown appears to work.. (I only had one
test previously so I hadn't noticed the issue..)

https://developers.google.com/appengine/docs/python/search/overview#Removing_Documents


On Thu, Aug 30, 2012 at 9:12 AM, jeffgnpc  wrote:

> I didn't see a LocalService object for the Search API, so I don't know how
> to reset the index after unit tests.  How are people unit testing their
> code around Search API?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/JMIDpqM1vhoJ.
> 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.
>



-- 
Jason Galea
ja...@lecstor.com

http://lecstor.com
https://github.com/lecstor
https://metacpan.org/author/LECSTOR
http://au.linkedin.com/in/jasongalea
https://plus.google.com/110776762575649383381
https://twitter.com/Lecstor

-- 
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] facebook scraping the site and showing 'Test Page: Success'

[Blast Radius]

We just launched tonight, though the code has been on our default instance 
for about 24 hours, and we add the URL as a status update in facebook, we 
see the default success page. When we share with /index.jsp we see the OG 
meta data. Here's the URL : http://nikeprotraining.sportchek.ca/

Is this a cache issue

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/I3AZIZh7omgJ.
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] Google Places API wrapper for Java GAE

[Rahul Tongia]

Hi There,

I want to use google places API from the service side at my Java appengine 
and GWT app. It is possible using URLFetch on places web services. Is there 
anyone who has written a library which converts the JSON response to Java 
objects.

This would save me considerable time in case some one has done that.

Thanks a lot

Rahul

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/jTUj3qc4sicJ.
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] One-time payment

[Tomáš Turek]

Hi,

I am wondering whether is it possible to send one-time payment to avoid 
exceeding free quotas. We have an application implemented by non-profit 
organization and have a budget which must be used upon a certain day. Is 
that possible at all?

Thanks!

Cheers,
Tomas

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/-PmjJNgEdhQJ.
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] Search API Unit Tests

[jeffgnpc]

I didn't see a LocalService object for the Search API, so I don't know how 
to reset the index after unit tests.  How are people unit testing their 
code around Search API?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/JMIDpqM1vhoJ.
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: MAX_BLOB_FETCH_SIZE value

[Stuart Langley]

This is the maximum size that can be fetched in a single call using 
BlobReader 
(https://developers.google.com/appengine/docs/python/blobstore/blobreaderclass) 
- The blob size that can be uploaded by users is effectively unlimited. 

On Thursday, 30 August 2012 05:05:56 UTC+10, Daniel Hans wrote:
>
> Hi there, 
>
> I have been trying to use MAX_BLOB_FETCH_SIZE to determine maximal size of 
> blobs that may be uploaded by the users. It is documented to be around 32 
> MB here [0] but the real value is actually less than one megabyte [1]. 
> Could anyone explain the difference to me or it is an issue and we should 
> create a new one for this? I can confirm that we do store larger files.
>
> Thank you,
> Daniel
>
> [0] 
> https://developers.google.com/appengine/docs/python/blobstore/overview#Introducing_the_Blobstore
> [1] 
> http://code.google.com/p/googleappengine/source/browse/trunk/python/google/appengine/api/blobstore/blobstore.py#83
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/ZhIhVpD-lKQJ.
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] Re: Weird Instance Scheduler

[Takashi Matsuo]

Hi Mos and everyone,

I'm trying to reproduce the issue about min idle instance which some of you
guys reported here in this thread, saying "Setting min idle instances
doesn't work for me".

My initial test is just with a simple helloworld Java application
multithread enabled, setting 1 min idle instance, and setting 1 min cron
job. I ran this test for about 2 and half days. I think it just worked as
expected. The resident instance had been alive and handled 3625 requests
during the test.

What I'm planning to do next is another experiment with an application with
Spring MVC. I'll update with the result hopefully next week.

At the same time, I'd like one of you to file an issue on our issue tracker
for this particular topic, 'Setting min idle instances doesn't work',
hopefully with expected behavior, actual results, a characteristic of the
application like average time for loading requests as well as normal
requests, etc. I've done a quick search on our issue tracker, and I don't
think there's any issue yet. If there's already an issue about it, please
let me know.

Thanks,


On Tue, Aug 28, 2012 at 2:13 AM, Carl Schroeder
wrote:

> Yep. Googlites, let us know what else you need to run this down.
>
>
> On Monday, August 27, 2012 10:05:41 AM UTC-7, Mos wrote:
>
>> In 
>> http://code.google.com/p/**googleappengine/issues/detail?**id=8004#c8
>> I described in detail a current example of the nonconforming
>> instance-handling of GAE.
>> Please check the comment, the screenshot and the log-file I filed there.
>>
>> Dear GAE-Team, what else do you need to fix this?  In this thread and in
>> several issues you should have more than enough proof and examples.
>>
>> Cheers
>> Mos
>>
>> On Mon, Aug 27, 2012 at 5:34 PM, Mos  wrote:
>>
>>> I saw the same behavior (as discussed before in the thread). Many other
>>> people reported this again and again on this mailing-list.
>>> Google has to acknowledge that the current implementation is buggy or
>>> the implementation works but doesn't make any sense in practice.
>>>
>>> Bye the way - The problem is not restricted to resident instances. From
>>> time to time the same happens for dynamic instances:
>>>
>>> One or more dynamic instances are running and are almost idle
>>> (sometimes really idle==no request or just one request is served).
>>> Request comes and starts a new dynamic instance, it goes through 30-40
>>> seconds of warmup, then request is served.
>>>
>>>
>>> On Mon, Aug 27, 2012 at 5:19 PM, Carl D'Halluin wrote:
>>>
 Hi Carl,

 I see exactly the same behaviour for my Java appengine app.
 Resident instance does nothing; instead idle instance is started, going
 through several seconds of warmup, then request is served.

 Regards


 On Mon, Aug 27, 2012 at 5:11 PM, Carl Schroeder 
 wrote:

> 2012-08-27 08:05 is the point in the logs. 1 Resident instance. No
> Dynamic instances.
> The request was sent to a cold starting Dynamic instance. Resident
> instance did nothing.
> Request took 18 seconds to serve.
>
>
> On Monday, August 27, 2012 2:16:25 AM UTC-7, Johan Euphrosine (Google)
> wrote:
>
>> On Mon, Aug 27, 2012 at 5:59 AM, Carl Schroeder
>>  wrote:
>> > Let me see if I understand this correctly: there is currently no
>> way on app
>> > engine to ensure that there is an instance ready to process
>> incoming
>> > requests for an app that has been idle for some period of time. Min
>> idle
>> > instances (labeled as Resident) sit there and do almost nothing
>> while user
>> > facing requests are instead sent to cold instance starts. If true,
>> that
>> > dovetails with what I have seen in the behavior of my app. For
>> python
>> > runtimes with sub-second spinup times, this is no big deal. For
>> java
>> > runtimes with spinup times in double digit seconds it is a
>> deal-breaker of a
>> > "feature".
>> >
>> > The problem seems to be that the scheduler thinks sending a request
>> to a
>> > non-existent dynamic instance is a better idea than using the
>> Resident
>> > instance for it's intended purpose: to serve requests when dynamic
>> instances
>> > are unable to. This is probably a corner case born of low traffic
>> conditions
>> > that allow user request serving dynamic instances to despawn.
>>
>> Hi Carl,
>>
>> That's not what we observed, as I corrected in the previous email:
>> """
>> Resident instances are used for processing incoming request if there
>> is no dynamic instance, but it is possible that the scheduler warm up
>> new dynamic instance to maintain the Min Idle Instance invariant.
>> """
>>
>> If you observe a different behavior please comment with your
>> application id and the timestamp of occurence and we can try to
>> fig

[google-appengine] Re: Algae - Application Template for Google App Engine

[Christopher Ramírez]

Thanks for your contribution Liya!

Have all the basics a modern web apps needs, including REST API's.

On Tuesday, August 28, 2012 4:06:53 PM UTC-6, Ilya Bagrak wrote:
>
> While building Turn-O-Phrase (http://turn-o-phrase.com) and LinkPeelr (
> http://linkpeelr.appspot.com) on GAE, I realized that both applications 
> shared a lot of boilerplate code I was either reinventing from scratch or 
> copy pasting across. 
>
> So for the last few months I've been working on a GAE application template 
> which I wish I had when I started tinkering with App Engine almost three 
> years ago.
>
> The result of this effort is Algae (http://green-algae.appspot.com), and 
> I am making it available to the app engine community at large. Algae 
> integrates de facto industry standards (like Twitter Bootstrap and HTML5 
> Boilerplate) with features every web app needs (like user management and 
> third-party authentication). And that's just scratching the surface...
>
> I am sharing it in the hope that the developer community finds it useful, 
> and I welcome your feedback and pull requests. The code is here: 
> http://github.com/ibagrak/algae
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/1Td9Ye9plosJ.
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] Error connecting to Google Cloud SQL

[Mike]

 0 down vote 
favorite
 
  
I am new to Google App engine and I have tried to run an demo application 
called guestbook to connect to Google cloud sql from the Google app engine 
with app-engine-sdk version 1-7.0. But each time I am getting an error 
saying "java.lang.IllegalStateException: System property rdbms.driver must 
be set at 
com.google.appengine.api.rdbms.dev.LocalRdbmsServiceLocalDriver.registerDriver(LocalRdbmsServiceLocalDriver.java:80)".
 
I double check my code and every thing looks ok, and I still have no glue 
where the error coming from. 

Below is a snippet of my connection code :

c = 
DriverManager.getConnection("jdbc:google:rdbms://my_instance/my_database");

and mysql-connector-java-5.1.21-bin is in the class path,

and I have enable Google cloud sql in the Google app engine,

and I have checked the use of Google Cloud instance in the app engine as 
well with the my instance of the database, database name, login , and 
password,

and I am using Eclipse Juno.

I think I have missed something important; so would you please help me if 
you know what I have missed.

Thank you very much in advance,

Minh

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/WLctVZ2jxPsJ.
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] Error connecting to Google Cloud SQL

[Mike]

0 down vote 
favorite
 
  
I am new to Google App engine and I have tried to run an demo application 
called guestbook to connect to Google cloud sql from the Google app engine 
with app-engine-sdk version 1-7.0. But each time I am getting an error 
saying "java.lang.IllegalStateException: System property rdbms.driver must 
be set at 
com.google.appengine.api.rdbms.dev.LocalRdbmsServiceLocalDriver.registerDriver(LocalRdbmsServiceLocalDriver.java:80)".
 
I double check my code and every thing looks ok, and I still have no glue 
where the error coming from. 

Below is a snippet of my connection code :

c = 
DriverManager.getConnection("jdbc:google:rdbms://my_instance/my_database");

and mysql-connector-java-5.1.21-bin is in the class path,

and I have enable Google cloud sql in the Google app engine,

and I have checked the use of Google Cloud instance in the app engine as 
well with the my instance of the database, database name, login , and 
password,

and I am using Eclipse Juno.

I think I have missed something important; so would you please help me if 
you know what I have missed.

Thank you very much in advance,

Minh

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/yvwX-RoMHK4J.
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] MAX_BLOB_FETCH_SIZE value

[Daniel Hans]

Hi there, 

I have been trying to use MAX_BLOB_FETCH_SIZE to determine maximal size of 
blobs that may be uploaded by the users. It is documented to be around 32 
MB here [0] but the real value is actually less than one megabyte [1]. 
Could anyone explain the difference to me or it is an issue and we should 
create a new one for this? I can confirm that we do store larger files.

Thank you,
Daniel

[0] 
https://developers.google.com/appengine/docs/python/blobstore/overview#Introducing_the_Blobstore
[1] 
http://code.google.com/p/googleappengine/source/browse/trunk/python/google/appengine/api/blobstore/blobstore.py#83

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/HhmL7qj75S0J.
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] Using @ElementCollection to persist a Collection of Enum

[roberto_sc]

I'm moving from JPA 1 to JPA 2 in my Gooogle App Engine project, and for 
that I changed the annotations for collections of enums, like this case:

//  @OneToMany(cascade = CascadeType.ALL) // JPA 1
@ElementCollection(targetClass=PositioningType.class)
private List bestPositionings;


PositioningType is an enum that is not annotated.

That code is giving me the following exception:

javax.persistence.PersistenceException: The MetaData for the element class 
"com.olympya.datamodel.model.PositioningType" of the collection field 
"com.olympya.datamodel.model.Player.bestPositionings" was not found.
at 
org.datanucleus.api.jpa.NucleusJPAHelper.getJPAExceptionForNucleusException(NucleusJPAHelper.java:302)
at 
org.datanucleus.api.jpa.JPAEntityTransaction.commit(JPAEntityTransaction.java:122)
at com.olympya.Services.mergeUser(Services.java:102)
...
Caused by: org.datanucleus.exceptions.NucleusUserException: The MetaData for 
the element class "com.olympya.datamodel.model.PositioningType" of the 
collection field "com.olympya.datamodel.model.Player.bestPositionings" was not 
found.
at 
com.google.appengine.datanucleus.scostore.AbstractFKStore.(AbstractFKStore.java:120)
at 
com.google.appengine.datanucleus.scostore.FKListStore.(FKListStore.java:83)
at 
com.google.appengine.datanucleus.DatastoreManager.newFKListStore(DatastoreManager.java:472)
at 
org.datanucleus.store.mapped.MappedStoreManager.getBackingStoreForCollection(MappedStoreManager.java:798)
at 
org.datanucleus.store.mapped.MappedStoreManager.getBackingStoreForField(MappedStoreManager.java:709)
at org.datanucleus.store.types.sco.backed.ArrayList.(ArrayList.java:99)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
...

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/8i6aCuw4COgJ.
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] Re: Hosting static files on GAE and using own domain.

[Omne]

Thank you all for your replies.

I used Eclipse because I had already downloaded it and I started to figure 
out how to work with it, I didn't want to start again with something new 
like Python...

I simply copied all my website, its files and folders, to "myproject/war" 
and it was really simpler than I thought to upload it. I also linked my 
domain with Google Apps and added it my GAE app/website. my website is now 
live, but I have a few problems...

*1- *My website is currently on www subdomain and I have to redirect my 
root domain to it, apparently GAE doesn't allow me to host on the root 
domain and it's making some problems for me, for example I couldn't verify 
my root domain for Norton Norton Safe Web, because it requires to add a 
meta tag or a file to root domain. is there a way to host my website/app on 
the root domain instead?

*2-* I'm not sure why my website isn't indexed by Google yet, it's about a 
week that my website is online, I've verified and "Fetch as Google" in 
Google Webmaster Tools and I've links to it from my FB fan page and 
Twitter... do you think it's too soon to appear in the index? or have I 
done something wrong with GAE that doesn't allow Google to index it?

On Sunday, August 19, 2012 8:25:11 PM UTC-7, Robert Fischer wrote:
>
> Sorry, the logic to see if it's localhost isn't sound.
>
> This is a bit more robust and works to redirect users to the custom domain 
> (www.dealscorcher.com in my case):
>
> class HomepageHander(webapp2.RequestHandler):
> def get(self):
> if (self.request.url.lower().find('dealscorcher.com') is -1 and
> self.request.url.lower().find('localhost') is -1):
> self.redirect('http://www.dealscorcher.com')
> return
>
> -Robert Fischer
> www.DealScorcher.com
>
> On Sun, Aug 19, 2012 at 8:14 PM, Robert Fischer 
> 
> > wrote:
>
>> Hi Omne,
>>
>> I was trying to say you can check the 
>> url
>>  of 
>> the 
>> Requestobject
>>  to generate a redirect from 
>> appid.appspot.com to whatever your domain is.
>>
>> Here's a quick snippet of code you can put at the beginning of your 
>> HomepageHandler's get method. It will redirect all *.appspot.com urls to 
>> your appid. I added my local address to my development server as well so I 
>> can still run the devserver.
>>
>> class HomepageHander(webapp2.RequestHandler):
>> def get(self):
>> if (self.request.url.lower() is not 'http://www.dealscorcher.com' 
>> or
>> self.request.url.lower() is not 'http://localhost:'):
>> self.redirect('http://www.dealscorcher.com')
>> return
>>
>> -Robert Fischer
>> www.DealScorcher.com
>>
>
Robert, thank you for the help, but I'm not sure what is the " 
HomepageHandler's get method" ? where should I add this? 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/bDW0vIrom6AJ.
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.