[jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1654) BlockContainerShutdownInterceptor does not immediately reject invocations once EJBContainer stop is requested

[Paul Ferraro (JIRA)]

BlockContainerShutdownInterceptor does not immediately reject invocations once EJBContainer stop is requested
-------------------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1654
                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1654
             Project: EJB 3.0
          Issue Type: Bug
          Components: core
    Affects Versions: 1.0.0-Beta11
            Reporter: Paul Ferraro
            Assignee: Paul Ferraro
             Fix For: 1.0.0-Beta12, 1.1.0-Beta1


During EJBContainer stop(), the container will wait until all EJB invocation complete before stopping the container.  However, the RWLock employed by the EJBContainer does not currently use a fairness policy.  This can cause a flurry of new invocations to block shutdown of the container.
Also, the tryLock() used in BlockContainerShutdownInterceptor will not respect the fairness policy of the RWLock.
tryLock(0, TimeUnit.SECONDS), on the other hand, shares the same general behavior as tryLock(), but will respect the fairness policy, i.e. it will immediately return false if some other thread is waiting on the acquisition of a write 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