[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3531) Add specific exception for lock failure on @Synchronized

Shane Bryzak (JIRA) jira-events at lists.jboss.org
Wed Oct 8 21:18:20 EDT 2008


     [ https://jira.jboss.org/jira/browse/JBSEAM-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shane Bryzak closed JBSEAM-3531.
--------------------------------

    Resolution: Done


Now it will throw org.jboss.seam.core.LockTimeoutException.

> Add specific exception for lock failure on @Synchronized
> --------------------------------------------------------
>
>                 Key: JBSEAM-3531
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3531
>             Project: Seam
>          Issue Type: Feature Request
>         Environment: Seam 2.0.2 FP
>            Reporter: Terry
>            Assignee: Shane Bryzak
>            Priority: Trivial
>             Fix For: 2.1.0.GA
>
>
> It would be nice to if some specific exception can replace IllegalStateException in cases where lock failes due to too many requests for a component; eg a Session component. It currently throws.
> java.lang.IllegalStateException: could not acquire lock on @Synchronized component:
> Specific exception would be help to display appropriate message, eg server too busy ....

-- 
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

        



More information about the seam-issues mailing list