Bugs item #854207, was opened at 2003-12-04 22:07 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=854207&group_id=22866
Category: JBossMQ Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: E.Sriram (esriram) Assigned to: Nobody/Anonymous (nobody) Summary: Too much synchronization in JMSTopic Initial Comment: Is there a way the synchronization overhead can be minimized in the addMessage() method of org.jboss.mq.server.JMSTopic class. (Release 3.2.1) synchronizing on the "durQueues" seems very very costly. I feel that synchronization is done only to make the Map thread safe against any subscribers being added/removed. I feel that all addMessages can be unsynchronized and a clone of the map can be made when a subscriber is being added/removed. Is there any API present in concurrent.jar which will lock only when add/remove of subscriber is done?? thanks, E.Sriram ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=854207&group_id=22866 ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
