Feature Requests item #1049914, was opened at 2004-10-19 12:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376688&aid=1049914&group_id=22866
Category: None Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Alexei Yudichev (sflexus) Assigned to: Nobody/Anonymous (nobody) Summary: DeadockDetection: print stack trace of waitingResource? Initial Comment: It is very good that ApplicationDeadlockException is now very verbose. However, it would make finding the deadlock cause a piece of cake if it also would include stack trace of the other (waiting) thread. If the application is complex, only knowing two bean names is not enough for me to guess where was the other place that current transaction deadlocked with. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376688&aid=1049914&group_id=22866 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
