[appengine-java] Re: new stack traces after upgrading to SDK 1.2.5
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. 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. :) --~--~-~--~~~---~--~~ 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 google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: new stack traces after upgrading to SDK 1.2.5
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 same error after upgrading to 1.2.5. I reverted to 1.2.2 and the error 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. 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. :) --~--~-~--~~~---~--~~ 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 google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: new stack traces after upgrading to SDK 1.2.5
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. Guice prints a similar stacktrace for its reference finalizer too, also as INFO. Cheers, Yegor On Sep 4, 1:41 pm, Vince Bonfanti vbonfa...@gmail.com wrote: After upgrading to SDK 1.2.5, I've noticed a set of stack traces that show up in both the development environment and on the production server. These only appear if the logging level is set to INFO, and they show up as INFO logs on the production server. I'm pretty sure these are new in SDK 1.2.5 since I've been running at the INFO logging level for quite some time. They only happen for the first request after the application has been restarted. From my production server: 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.inheritableThreadLocals. Reference finalizer threads will inherit thread local values. com.google.appengine.repackaged.com.google.common.base.FinalizableReference Queue init: Failed to start reference finalizer thread. Reference cleanup will only occur when new references are created. java.lang.reflect.InvocationTargetException at com.google.appengine.runtime.Request.process-ad303eae7c610e90(Request.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Method.java:40) at com.google.appengine.repackaged.com.google.common.base.FinalizableReference Queue.init(FinalizableReferenceQueue.java:124) at com.google.appengine.repackaged.com.google.common.labs.misc.InterningPools$ WeakInterningPool.clinit(InterningPools.java:104) at com.google.appengine.repackaged.com.google.common.labs.misc.InterningPools. newWeakInterningPool(InterningPools.java:48) at com.google.appengine.repackaged.com.google.io.protocol.ProtocolSupport.cli nit(ProtocolSupport.java:55) at com.google.apphosting.api.DatastorePb$Query.init(DatastorePb.java:1072) at com.google.apphosting.api.DatastorePb$Query$1.init(DatastorePb.java:2355) at com.google.apphosting.api.DatastorePb$Query.clinit(DatastorePb.java:2355) at com.google.appengine.api.datastore.QueryTranslator.convertToPb(QueryTransla tor.java:27) at com.google.appengine.api.datastore.DatastoreServiceImpl$PreparedQueryImpl.c onvertToPb(DatastoreServiceImpl.java:357) at com.google.appengine.api.datastore.DatastoreServiceImpl$PreparedQueryImpl.r unQuery(DatastoreServiceImpl.java:339) at com.google.appengine.api.datastore.DatastoreServiceImpl$PreparedQueryImpl.a ccess$100(DatastoreServiceImpl.java:269) at com.google.appengine.api.datastore.DatastoreServiceImpl$PreparedQueryImpl$1 .iterator(DatastoreServiceImpl.java:303) at org.apache.jsp.test.listEntities_jsp._jspService(listEntities_jsp.java:49) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) ...truncated --~--~-~--~~~---~--~~ 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 google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: new stack traces after upgrading to SDK 1.2.5
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. :) --~--~-~--~~~---~--~~ 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 google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: new stack traces after upgrading to SDK 1.2.5
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 google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
