[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1272) SynchronizationInterceptor#aroundInvoke should not be synchronized

Gavin King (JIRA) jira-events at lists.jboss.org
Tue May 1 03:01:30 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBSEAM-1272?page=all ]

Gavin King closed JBSEAM-1272.

    Fix Version/s: 1.3.0.BETA1
       Resolution: Done
         Assignee: Gavin King

Ooops! Thanks, fixed in CVS.

> SynchronizationInterceptor#aroundInvoke should not be synchronized
> ------------------------------------------------------------------
>                 Key: JBSEAM-1272
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1272
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.1.GA
>         Environment: Seam 1.2.1GA
>            Reporter: Paul Lorenz
>         Assigned To: Gavin King
>             Fix For: 1.3.0.BETA1
> Because SynchronizationInterceptor#aroundInvoke is synchronized, the locking code inside the method is accessed serially (at least for Session scoped JavaBeans). This means that access to the bean will be serialized by synchronizing on the interceptor, rather than on the RentrantLock. The also means that the timeout will never be used, and if something deadlock inside the interceptor, things trying to enter the block will also deadlock indefinitely. This caused our production system to lock up today. We were unable to determine if there is some other reason for the synchronized being on the method, but couldn't think of one, since the scope for the two methods of synchronized is the same.
> As an aside, Seam is great! Thank you for all the hard work.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list