[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4473) When a "Concurrent call to conversation" exception is thrown it should be possible to know what code holds the lock
[
https://jira.jboss.org/jira/browse/JBSEAM-4473?page=com.atlassian.jira.pl...
]
Francisco Jose Peredo Noguez commented on JBSEAM-4473:
------------------------------------------------------
I think it should be possible to create a solution for this issue using the solution I
proposed for JBSEAM-4472 as guidance
When a "Concurrent call to conversation" exception is
thrown it should be possible to know what code holds the lock
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-4473
URL: https://jira.jboss.org/jira/browse/JBSEAM-4473
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.1.GA
Reporter: Francisco Jose Peredo Noguez
Please modify the org.jboss.seam.core.Manager code so that when a "Concurrent call
to conversation" exception is thrown 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