I've got the same stack trace. I reveted back to 1.2.2 due and this
exception disappeared.
On Sep 4, 3:14 pm, Vince Bonfanti vbonfa...@gmail.com wrote:
That's fine. :)
I just wanted to make sure someone was aware of this, since it
appeared to be something new introduced with the latest SDK.
I would recommend setting:
com.google.appengine.repackaged.com.google.common.base.FinalizableReferenceQueue.level=WARNING
in your logging.properties file to disable this log message. It's harmless,
but annoying.
On Tue, Sep 8, 2009 at 12:49 PM, anjolight anjoli...@gmail.com wrote:
I got the
Vince,
If you are interested the reason for the exception is that App Engine
does not support threads. Reference finalizer usually runs as a
separate thread. In this case the finalizer (correctly) failed to
initialize. However, it looks like finalizer is not a critical
component in this context.
That's fine. :)
I just wanted to make sure someone was aware of this, since it
appeared to be something new introduced with the latest SDK.
On Fri, Sep 4, 2009 at 4:14 PM, Toby Reyeltsto...@google.com wrote:
It's a message that you can safely ignore. There is a reason it's logged at
INFO. :)
Vince,
I'm still using SDK 1.2.2 and I am getting a very similar info
message.
--~--~-~--~~~---~--~~
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
