Comment #28 on issue 288 by mcculls: FinalizableReferenceQueue still leaks
http://code.google.com/p/google-guice/issues/detail?id=288
Here's a potential solution, which adds a new property:
-Dguice.executor.class
* This property can be used to pass a custom java.util.concurrent.Executor
implementation class to Guice.
* Setting it to the empty string (-Dguice.executor.class=) will disable the
Guice Finalizer thread completely.
* If this property is unset then Guice will use a simple Executor that
creates a new thread (as at the moment).
This should avoid the main coupling issue wrt. who creates the actual
thread (the Finalizer runnable is already decoupled) and also provide some
means for shutting down the task from the outside without having to add a
public shutdown API.
Note: I'm currently testing this patch in an experimental sisu-guice build:
https://github.com/sonatype/sisu-guice/commit/d5dc781d31a625a9596cd0fcbe3c54fa15ee28ce
Attachments:
GUICE_ISSUE_288_20110111.txt 5.9 KB
--
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.
