Oho. False alarm on #2 and #3 - I realized that I'm failing to close a PersistenceManager, which may account for the intermittent problem on that account.
On Nov 5, 5:09 pm, "Chris C." <[email protected]> wrote: > Ran into a few more "first-time" problems, that I thought I'd throw > onto the list here: > > 1. Failure to send outgoing operations. While the robot appears to be > responding to BLIP_SUBMITTED just fine, the outgoing operations JSON > is empty. This comes and goes, and I can't find a good reason for it. > It does not appear to be my robot. > > 2. Three items logged in the info: > > com.google.appengine.repackaged.com.google.common.base.FinalizableReference > Queue > $SystemLoader loadFinalizer: Not allowed to access system class loader > com.google.appengine.repackaged.com.google.common.base.internal.Finalizer > getInheritableThreadLocalsField: Couldn't access > Thread.inheritableThreadLoc > com.google.appengine.repackaged.com.google.common.base.FinalizableReference > Queue > <init>: Failed to start reference finalizer thread. > > These started showing up today. I have changed the robot recently, and > it now queries its datastore during operations, so perhaps that has > something to do with this error? Maybe I'm doing something wrong > (though it's very simple querying/storing, almost exactly copied from > the tutorials). > > 3. Very high CPU usage about every other request: requests that are > successful take some small amount of CPU-milliseconds, usually between > 30-60. But every other, or every few times, a request (identical to > previous requests) will take something like 7,157 or 8,029 CPU- > milliseconds; invariably, requests that end up with numbers that high > never respond back to the wave (that is, the blip content is never > updated, even if the outgoing operations contain the expected data). > Additionally, the high-CPU-time requests always include the errors > mentioned in #2. > > So...ideas? > > Thanks, > Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" 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-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
