[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4472) When a "could not acquire lock on @Synchronized component" exception is thrown it should be possible to know what code holds the lock

[ https://jira.jboss.org/jira/browse/JBSEAM-4472?page=com.atlassian.jira.pl... ] Francisco Jose Peredo Noguez updated JBSEAM-4472: ------------------------------------------------- Summary: When a "could not acquire lock on @Synchronized component" exception is thrown it should be possible to know what code holds the lock (was: When a "could not acquire lock on @Synchronized component" excepction is thrown it should be possible to know what code holds the lock) Description: Please modify the default SynchronizationInterceptor so that when a "could not acquire lock on @Synchronized component" exception is thrown one can easily find out what code holds the lock (was: Please modify the default SynchronizationInterceptor so that when a "could not acquire lock on @Synchronized component" exception one can easily find out what code holds the lock) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira