[jboss-jira] [JBoss JIRA] Updated: (JBAS-5027) Support object passivation with FIELD granularity clustered webapps

[Dimitris Andreadis (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-5027?page=all ]

Dimitris Andreadis updated JBAS-5027:
-------------------------------------

    Fix Version/s: JBossAS-5.0.0.CR2
                       (was: JBossAS-5.0.0.CR1)

Pushing non-critical issues to the next CR2. If you think they are critical for CR1, please re-schedule them.

> Support object passivation with FIELD granularity clustered webapps
> -------------------------------------------------------------------
>
>                 Key: JBAS-5027
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5027
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: JBossAS-5.0.0.CR2
>
>
> The AS 5 clustered webapp session passivation feature is not very useful when FIELD is used, since the pojos stored in the sessions are not part of the session 's part of the JBoss Cache tree. They are in an internal area that is a sibling to the sessions.[1] So, evicting the session tree does not evict the pojos.  Presumably most of the memory is used by the pojos.
> Solution is for JBossCacheManager to programatically establish a regular JBC eviction region for the pojo storage area. To configure this the following elements will be added to jboss-web.xml's passivation-config:
> <passivation-config>
>    <max-objects>10</max-objects>
>    <object-max-idle-time>600</object-max-idle-time>
> <passivation-config>
> These values will be translated into the JBC LRUPolicy's "maxNodes" and "timeToLiveSeconds" configuration properties.
> [1] They are in a sibling area to the sessions since the pojos can be shared between sessions.  The pojos are scoped to the webapp.

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