Hi David. I believe you're referring to a different problem. The default
timeout limit for URL Fetch requests is 5 seconds. If Twitter's API has
especially high latencies (i.e. > 5 seconds), your requests may be timing
out. If you can, I suggest modifying the library to have a higher timeout --
currently, you can configure this up to 10 seconds.

http://code.google.com/appengine/docs/java/urlfetch/overview.html#Requests

- Jason

On Fri, Oct 16, 2009 at 12:51 PM, [email protected] <[email protected]>wrote:

>
>
> Twitter API calls (using twitter4j) from App Engine fail far more
> often than they succeed, when the same calls work fine from the same
> code running on a non-App Engine platform.
> http://mrblog.org/2009/10/16/twitmart-ported-off-of-google-app-engine/
>
> Are you saying this is going to be fixed?  That's really good news, if
> so.
>
> On Oct 6, 9:26 am, Don Schwarz <[email protected]> wrote:
> > This was not caused by any problem with the URLFetch service.  As you can
> > see from our Status Site, URLFetch is fine:
> http://code.google.com/status/appengine/detail/urlfetch/2009/10/06#ae...
> >
> > This was most likely caused by a request exceeding the 30 second deadline
> > while initializing the URLFetchServicePb class.  I believe you've posted
> > about this problem in the past.
> >
> > We have what we think is a general fix for this issue in the next
> release,
> > which is due out very shortly.  In the mean time, I've reloaded your app
> > (but you can do this yourself by redeploying if necessary).
> >
> > Sorry for the inconvenience,
> > Don
> >
> > On Tue, Oct 6, 2009 at 11:20 AM, hansamann <[email protected]
> >wrote:
> >
> >
> >
> >
> >
> > > Hi all,
> >
> > > since at least a couple of hours I can see this exception in the logs:
> >
> > > [groovytweets/79.336780622574504562].<stdout>: StackTrace Sanitizing
> > > stacktrace:
> > > java.lang.NoClassDefFoundError: Could not initialize class
> > > com.google.appengine.api.urlfetch.URLFetchServicePb$URLFetchRequest
> > >        at
> com.google.appengine.api.urlfetch.URLFetchServiceImpl.convertToPb
> > > (URLFetchServiceImpl.java:77)
> > >        at com.google.appengine.api.urlfetch.URLFetchServiceImpl.fetch
> > > (URLFetchServiceImpl.java:29)
> > >        at twitter4j.http.Response.<init>(Response.java:82)
> > >        at twitter4j.http.HttpClient.httpRequest(HttpClient.java:459)
> > >        at twitter4j.http.HttpClient.get(HttpClient.java:420)
> > >        at twitter4j.Twitter.get(Twitter.java:280)
> > >        at twitter4j.Twitter.get(Twitter.java:330)
> > >        at twitter4j.Twitter.getFriendsTimeline(Twitter.java:678)
> > >        at sun.reflect.GeneratedMethodAccessor920.invoke(Unknown Source)
> > >        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> > >        at java.lang.reflect.Method.invoke(Method.java:40)
> >
> > > Why is it that NoClassDefFoundErrors have to be thrown, it sounds like
> > > someone removed a jar file out of the running application's memory...
> > > hmm. This happened quite a lot of times now, is that really the
> > > 'official' exception whenever the service is down?
> >
> > > Cheers
> > > Sven
> >
>

--~--~---------~--~----~------------~-------~--~----~
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 [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to