[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4472) When a "could not acquire lock on @Synchronized component" excepction 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 commented on JBSEAM-4472:
------------------------------------------------------
The referenced forum thread now has an example implementation that makes it easy to know
what code is holding the lock
When a "could not acquire lock on @Synchronized component"
excepction is thrown it should be possible to know what code holds the lock
--------------------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-4472
URL: https://jira.jboss.org/jira/browse/JBSEAM-4472
Project: Seam
Issue Type: Feature Request
Components: Core, Exception Handling
Affects Versions: 2.1.1.GA
Reporter: Francisco Jose Peredo Noguez
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