Bugs item #745527, was opened at 2003-05-29 10:30 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=745527&group_id=22866
Category: JBossMQ Group: None Status: Open Resolution: None Priority: 5 Submitted By: john hutchinson (jamoville) Assigned to: Nobody/Anonymous (nobody) Summary: race condition with BasicQueue Initial Comment: This bug exists in all versions of jboss 3.X. and on Unix and windows I have an application that utilizes messaging to a great extent. When running many threads against your server a deadlock occurs. I ended up dumping the threads and windows informed me of a race condition with BasicQueue. Specifically one thread was waiting on a monitor that was already held by another thread and that thread was waiting on a monitor that the other thread had. The synchronized objects where unacknowledgedMessages and removedSubscribers. If needed I can supply the stack dump of both threads. I corrected this by removing all synch blocks in the BasicQueue class and any method that contained a synch block I made synchronized. This fixed the issue and gave the added benifit of increasing performance by 30 to 40 percent. I've attached the modified file ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=745527&group_id=22866 ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
