Changing this to a HashSet should solve my concerns about lock exclusivity as well since the more efficient algorithm means that even if the list grows large the time threads are competing for that lock will remain small.
In terms of how big of a problem this is, as I said in my post, I haven't fully quantified it, but it is showing up on our app monitoring as a point of contention for threads. You'd be surprised how quickly small things like this cause threads to pile up. Thanks for the quick response in making these changes, and for incorporating my suggestions for my earlier 2 posts. I'll be trying these out later today and will let you know if I see any problems. Thanks and regards, Brian. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880753#3880753 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880753 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
