[jboss-jira] [JBoss JIRA] Closed: (JBAS-7123) JBossCacheManager remains open to requests after shutdown

[Brian Stansberry (JIRA)]

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

Brian Stansberry closed JBAS-7123.
----------------------------------

    Fix Version/s: JBossAS-6.0.0.M2
                       (was: JBossAS-6.0.0.M3)
       Resolution: Done


> JBossCacheManager remains open to requests after shutdown
> ---------------------------------------------------------
>
>                 Key: JBAS-7123
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7123
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-5.1.0.GA
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-6.0.0.M1, JBossAS-6.0.0.M2
>
>
> The work Paul Ferraro did with LockValve ensures that typically application activity cannot reach the clustered session manager after its stop() processing executes, but testing is showing the StandardHostValve can end up causing calls to findSession that end up blowing up with an NPE.  That's the specific issue; in general, the methods in the Manager API need to be hardened to react properly if invoked during/after shutdown.
> Solution is to use the same semaphore that LockValve uses, but use it internally -- add tryLock/release calls around the relevant code. Once stop() processing proceeds, tryLock will fail and the methods can react appropriately.

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