How to reliably count active sessions and connected users ?

[gaboo]

Hello.

I'm using seam 2.0.0 and I'd like to cound the active sessions and connected users.

For session, I'm using two observer methods in an application scoped ejb to count :

@Observer("org.jboss.seam.postCreate.org.jboss.seam.web.session")
public void increaseUserCount() {
 userCount++;
}

@Observer("org.jboss.seam.preDestroyContext.SESSION")
public void decreaseUserCount() {
 userCount--;
}

For connected users, I use those two seam security events :

@Observer("org.jboss.seam.security.loginSuccessful")
public void increaseConnectedUserCount() {
 connectedUserCount++;
}

@Observer("org.jboss.seam.security.loggedOut")
public void decreaseConnectedUserCount() {
 connectedUserCount--;
}

Both solutions aren't ok. For example, sometimes I have a number of -1 for connected users. And for sessions, the number keeps high, so I don't know If a really catch all session ending.

Do you have / know a better idea ?

[gaboo]

A little bit more about this : the org.jboss.seam.security.loggedOut event is not raised when the web session expire and there was a connected user.

Can I consider this a seam bug or not ?

[shane.bryzak]

This isn't a bug. the loggedOut event is only raised when a user explicitly calls Identity.logout(), which doesn't happen when the session simply expires. I'm not sure which alternative to suggest, perhaps we need a new feature to support some kind of global session tracking.

[jacob.orshalick]

... perhaps we need a new feature to support some kind of global session tracking.

Sounds like a cool feature to me. Relates to an event requested in the comments of:

http://jira.jboss.com/jira/browse/JBSEAM-2257

"org.jboss.seam.destroyedSession". Maybe raise a JIRA issue for session tracking and link to 2257?