[jboss-jira] [JBoss JIRA] Updated: (JBAS-5981) ActiveSessions should have consistent meaning in both clustered and non-clustered session manager

[Remy Maucherat (JIRA)]

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

Remy Maucherat updated JBAS-5981:
---------------------------------

    Assignee: Paul Ferraro  (was: Remy Maucherat)


This looks implemented to me in trunk: JBossManager.getActiveSession() returns the local active sessions.

> ActiveSessions should have consistent meaning in both clustered and non-clustered session manager
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-5981
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5981
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-5.0.0.CR2
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>            Priority: Minor
>             Fix For: JBossAS-6.0.0.M3
>
>
> The "ActiveSessions" attribute of the non-clustered session manager returns the number of active sessions on the server.  In the clustered case, this attribute takes on a different meaning and returns the number of active sessions on all servers in the partition.   A separate "LocalActiveSessions" attribute returns just the active sessions on the local node.
> "ActiveSessions" should return the same value for both the clustered and non-clustered session manager.  The clustered session manager should replace "LocalActiveSessions" with an "ActiveReplicatedSessions" attribute that returns the total number of active sessions in the partition.
> Mod-cluster has an ActiveSessionsLoadMetric that determines the number of active sessions on the node using this attribute on the session manager.  Requiring the user to override the attribute name depending on whether or not they use session replication is rather sloppy.  Instead, this attribute should have a consistent meaning regardless of session manager implementation.

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