Comment #3 on issue 488 by [email protected]: 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
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" 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-guice-dev?hl=en.