From mcculls on June 17, 2010 09:11:10

IIRC this is just an info log message letting you know that Guice couldn't start the finalizer thread in the more restrictive GAE environment - your servlet should still work (if it doesn't then that's a different issue).

From sberlin on June 18, 2010 06:09:06

Not a bug, it's just an info message.

Status: Invalid

From vega113 on July 27, 2010 20:23:09

Thanks for the answers above. You are right, sberlin, The servlet still works, however as I mentione before, the servlet runs on GAE and when the exception happens it eats a lot of CPU - for example:
/installNew?id=*** 200 8303ms 13282cpu_ms 21api_cpu_ms 0kb gzip(gfe)
request to the same servlet that doesn't cause exception
/installNew?id=*** 200 1198ms 468cpu_ms 21api_cpu_ms 0kb gzip(gfe)

The exception happens all the time and its handling eats CPU=money.
So it's not "just an info message".
I really need advice on what can be done to reduce the CPU consumption at least by this exception handling, or event better to prevent the exception to happen.
Thanks

From vega113 on July 27, 2010 20:26:14

I just want to add that its really strange that Guice as a Google supported development doesn't integrate nicely with GAE.

From marius.andreiana on October 13, 2010 11:31:11

Please re-open this.
Info messages should be generated with proper logging, not exceptions.

From richpaul1 on January 05, 2011 14:02:37

My app is also experiencing this issue.

I agree with Marius.

This should be re-opened and fixed so that an exception is not thrown.

From mcculls on January 11, 2011 16:05:16

Note: the potential solution I recently attached for Issue 288 would also help this issue.

From nimbus4321 on February 08, 2011 10:33:01

This issue also occurs on WebSphere 7.x when the default JavaSE security policy is enabled. This is because the default policy prevents application code from creating threads (as per the EJB programming restrictions).

Note that I've also posted on issue 288 asking if the new fix to hat issue (from fry) addresses this issue too.

From icoloma on March 08, 2012 02:34:13

For the record, this is a workaround to put in your startup listener:

Logger.getLogger("com.google.inject.internal.util").setLevel(Level.WARNING);

From huseyn@guliyev.com on April 24, 2012 06:23:20

I agree that this issue should be dealt with. The resolution suggested in comment 9 is not a workaround, but rather a hideout.

From dward@versature.com on January 15, 2013 08:09:38

I also think this issue should be dealt with. Also comment 9 is not a workaround.

From Juan.Gentile@pnvillarreal.me on May 15, 2013 05:33:45

Please reopen this and treat it accordingly. If people end up reading this thread is for a reason. The exception is indicating an error failing to start... and access denied. That is not the normal info message one would expect to see in a log.

From mcculls on May 15, 2013 05:55:57

Note that the FinalizableReferenceQueue message came from an old embedded copy of Guava which started a background thread to handle cleanup of certain weak/soft collections. Guice trunk now includes Guava 11.0.1 that doesn't start a background thread for these collections, so this message will no longer occur.

From Juan.Gentile@pnvillarreal.me on May 15, 2013 05:57:37

thanks

From sowdri on July 03, 2013 06:45:48

I'm using Guice v3.0 + Guava v12.0 the issue still occurs. And its eating CPU.
For a request it took 47306ms.

Kindly fix this.

From mcculls on July 03, 2013 06:57:35

As mentioned above, Guice 3.0 embeds a local copy of Guava repackaged under a different package name. So adding Guava 12.0 to your classpath won't change anything because Guice will still use the old embedded code.

You either need to build Guice trunk locally and use that (at least until the next release is available), or look at http://search.maven.org/#artifactdetails%7Corg.sonatype.sisu%7Csisu-guice%7C3.1.5%7Cjar which is Guice trunk plus some extra patches (these patches include making Guava a proper dependency rather than embedded).

From deletedaccount on January 21, 2014 02:28:06

When is the next release available?  This is a serious problem.

Hi, did somene find how to fix that warning?

@kiitos6 it shouldn't happen if you use Guice 4.0

@mcculls Ok I am going to try. I only need to change the guice.jar? or I need another jar dependecy update too?
Thank you

Is working perfect with guice-4.0 and guice.assistedinject-4.0. Thanks