[ https://issues.apache.org/jira/browse/OWB-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901089#action_12901089 ]
Mark Struberg commented on OWB-444: ----------------------------------- Maybe my proposal was not yet clear enough: I like to keep those utils as members in BeanManagerImpl (with back-references), so for each WebApp we have exactly 1 BeanManagerImpl. And this has exactly 1 instance of each util. In this case we do not need any singletons anymore. Because our BeanManagerImpl has exactly the one needed (and correctly configured) util class at hand. To give you a few numbers: on a large JSF page I originally had more than 1 million WebBeansFinder invocations! Most of them come from our utils which most times need to resolve the BeanManagerImpl... I then at least removed redundant BeanManagerImp.getManager() calls and also removed the doPrivileged and now we are down to ~400.000 invocations. At the end of the day this still costs up to 20% of our performance, so I would not underestimate the effect! > Using Static Loggers in Shared ClassLoader > ------------------------------------------ > > Key: OWB-444 > URL: https://issues.apache.org/jira/browse/OWB-444 > Project: OpenWebBeans > Issue Type: Bug > Components: Core > Affects Versions: 1.0.0-alpha-1 > Reporter: Gurkan Erdogdu > Assignee: Gurkan Erdogdu > Fix For: 1.0.0-GA > > > Errors of using static loggers in shared classloaders environments -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.