Hi, currently we're running into an issue with using Guice in our application with using a combination of child injectors and multibindings.
The issue is that we have a servlet based application that has one global injector that spans the sessions. Each session has (at least) one childinjector level to allow the relevant session level instances to be directly bound. We are also using child injectors to bind session specific sets of interface implementations in these child injectors. During a load test we found out, that this approach leads to each session adding to the blacklist in the global injector, since each multibinding in each session gets a new uniqueid. This lead to the global blacklist filling up to around 500k entries which are never cleaned up. This seems to be the same issue as described here: https://code.google.com/p/google-guice/issues/detail?id=756 Is there any way to avoid this? Currently the only solution I would see for it is extracting the multibindings to the top level and do possible user specific filtering manually. Regards, Johannes -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice. For more options, visit https://groups.google.com/groups/opt_out.
