[google-appengine] Re: 1.1.6 urlfetch with largish payload fails with ApplicationError: 2 (35, 'Resource temporarily unavailable')

2008-11-21 Thread Marzia Niccolai
Hi, Would it be possible for you to provide the code you are using that fails with this error? Does increasing the time out allow the request to go through? -Marzia On Fri, Nov 21, 2008 at 1:13 PM, Gijsbert <[EMAIL PROTECTED]>wrote: > > Hi, > > Since upgrading to 1.1.6 I get ApplicationError:

[google-appengine] Re: 1.1.6 urlfetch with largish payload fails with ApplicationError: 2 (35, 'Resource temporarily unavailable')

2008-11-21 Thread Gijsbert
Hi Marzia, The code is nothing special, it boils down to this: urlfetch.fetch(amazonurl, payload=jpegfile, urlfetch.PUT, headers=amazonheaders, allow_truncated=false) (I'm using s3fetch() from this thread: http://groups.google.com/group/google-appengine/browse_thread/thread/83bae2a7f93a476b).

[google-appengine] Re: 1.1.6 urlfetch with largish payload fails with ApplicationError: 2 (35, 'Resource temporarily unavailable')

2008-11-24 Thread Marzia Niccolai
Hi Gijsbert, I'm not able to replicate this on my Mac, but I'm using Python 2.5.1 (Python 2.5 (r25:51918, Sep 19 2006, 08:49:13) [GCC 4.0.1 (Apple Computer, Inc. build 5341)] on darwin). Using a 60KB payload goes through fine for me on 1.1.7 without modifying urlfetch at all. Perhaps if someone

[google-appengine] Re: 1.1.6 urlfetch with largish payload fails with ApplicationError: 2 (35, 'Resource temporarily unavailable')

2008-11-25 Thread Gijsbert
Hi Marzia, It would be interesting to try with a much bigger payload (towards 1MB) since it would be triggered by the network device not being able to deliver the data as fast as urlfetch can produce it (and sending it to a host not on your own network, which slows down the transfer as well). Ch