Yes. I'm quite sure. A couple of examples. A tipical request with normal execution time and without FinalizableReferenceQueue 12-10 10:40PM 32.484 /url.... 200 83ms 160cpu_ms 85api_cpu_ms
A request with FinalizableReferenceQueue: 12-10 10:36PM 22.306 /url.... 200 4888ms 7280cpu_ms 85api_cpu_ms fabrizio On Dec 11, 6:17 am, Rusty Wright <[email protected]> wrote: > Are you sure the slowness is caused by whatever is generating this exception? > > > > fhtino wrote: > > Vince, > > > ok, it's harmless, but the response is very slow. 5000ms or more > > instead of 200ms. > > In my case it's a problem. > > > Any idea/solution? > > > fabrizio > > > On Dec 5, 7:07 pm, Vince Bonfanti <[email protected]> wrote: > >> The exception is harmless. Add this to your logging.properties file to hide > >> it: > > >> com.google.appengine.repackaged.com.google.common.base.FinalizableReference > >> Queue.level=WARNING > > >> There was previous discussion of this (search > >> for FinalizableReferenceQueue). > > >> Vince > > > -- > > > 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 > > athttp://groups.google.com/group/google-appengine-java?hl=en. -- 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.
