Hi folks, I've been doing some EJB profiling lately and one of the cpu hot spots was related to the doPrivileged() method.
I've got a classic facade design : a stateful session bean, accessible remotely by clients, which uses a number of BMP EJB's to fetch data. The entity beans are only accessible locally. The facade does for each entity bean two method calls; to get two properties. For each call doPrivileged pops up. The trouble is that there are a lot of entity beans to address for one client request. And in the end the method calls add up to a real performance issue. Is there a way to prevent, switch off, whatever, security checks for entity beans ? (Or is this doPrivileged call related to something else entirely ?) In my case it won't make much sense to check the entity beans anyway. If the user obtained an instance of the session bean, it implicitely means the data must be accessible too. Many thanks for any clue ! Jan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976268#3976268 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976268 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
