Re: Issue 488 in google-guice: Exception in Finalizer in AppEngine

[google...@googlecode.com]

Comment #3 on issue 488 by vega...@gmail.com: Exception in Finalizer in
AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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

[google...@googlecode.com]

Comment #4 on issue 488 by vega...@gmail.com: Exception in Finalizer in
AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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

[google...@googlecode.com]

Comment #5 on issue 488 by marius.a...@gmail.com: Exception in Finalizer in
AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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

[google...@googlecode.com]

Comment #6 on issue 488 by richpaul1: Exception in Finalizer in AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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.

[google...@googlecode.com]

Comment #7 on issue 488 by mcculls: Exception in Finalizer in AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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

[google...@googlecode.com]

Comment #8 on issue 488 by nimbus4...@gmail.com: Exception in Finalizer in
AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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.

[google...@googlecode.com]

Comment #9 on issue 488 by icol...@gmail.com: Exception in Finalizer in
AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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

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

[google...@googlecode.com]

Comment #10 on issue 488 by hus...@guliyev.com: Exception in Finalizer in
AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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

[google...@googlecode.com]

Comment #11 on issue 488 by dw...@versature.com: Exception in Finalizer in
AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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

[google...@googlecode.com]

Comment #12 on issue 488 by Juan.Gen...@pnvillarreal.me: Exception in

Finalizer in AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[google...@googlecode.com]

Comment #13 on issue 488 by mccu...@gmail.com: Exception in Finalizer in
AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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.

[google...@googlecode.com]

Comment #14 on issue 488 by Juan.Gen...@pnvillarreal.me: Exception in

Finalizer in AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

thanks

[google...@googlecode.com]

Comment #15 on issue 488 by sow...@gmail.com: Exception in Finalizer in
AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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.

[google...@googlecode.com]

Comment #16 on issue 488 by mccu...@gmail.com: Exception in Finalizer in
AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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).

[google...@googlecode.com]

Comment #17 on issue 488 by deleteda...@gmail.com: Exception in Finalizer
in AppEngine
http://code.google.com/p/google-guice/issues/detail?id=488

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