NMB_OF_SESSIONS

RocketRod

There appears to be a problem with this when a user is timed out instead of logging off. I'm not sure how this function calculates how a user is logged on but I am getting counts of 2 for a user when they are definitely only logged on once.

Cheers Rod

tford

Are you positive the first instance is timed out when you are expecting it not to be counted?

RocketRod

Also if you are in test mode and you don't log off testing your app but you then go and make some changes and reload the app, when you log in again to test I get the issue. Look I maybe doing something wrong in my process but I've followed it through the log and it comes back with a value of 2 and I only have one test user logged on. I guess support can easily clear it up as to if its me and something I'm doing wrong or the function.

Cheers Rod

aware_support

There are two places where timeout is maintained:
1) On the server (managed by the Aware IM server)
2) On the web server (managed by Tomcat)

It is possible that one session times out while the other remains active if your timeout values for both servers are different (there is a special thread somewhere about it). The NMB_OF_SESSIONS function calculates server sessions, not web server sessions, so it is possible that one of your server sessions is still alive. You may want to check your timeout settings to make sure that both timeout values are sync'ed