OK - Following on from some comments in a different post, thought I would start a new thread for this one.
I have a loginNotification (When loginNotification is received) - the code is below.
IF NOT(EXISTS UserLog WHERE (UserLog.Mem_Login=LoggedInSystemUser.LoginName AND UserLog.LogoutTime IS UNDEFINED))THEN CREATE UserLog WITH UserLog.LoginTime=CURRENT_TIMESTAMP,UserLog.Mem_Num=LoggedInSystemUser,UserLog.RerringURL=LoginNotification.ReferringURL, UserLog.RemoteAddress=LoginNotification.RemoteAddress, UserLog.SessionID=LoginNotification.SessionId
There is also a very simple logoutNotification
FIND UserLog WHERE LoggedInSystemUser IN UserLog.Mem_Num AND UserLog.LogoutTime IS UNDEFINED
UserLog.LogoutTime=CURRENT_TIMESTAMP
This functionality works fine for most users EXCEPT Firefox users. For some reason, their login process fires the loginNotification multiple times (up to 12) giving each attempt a separate session ID. My concern is that if all my users were firefox users, the server would very quickly run out of session resources. Significantly, over the run up to Christmas when there was a lot of extra activity on the servers, my AIM stopped working twice with tcp Port 9000 blocked. (Restarting the AwareIM service cured this - but not before some irate phone calls)
Does anyone know what is happening and how to cure this? either in the firefox browser or maybe some timeout variable within AIM that needs tweaking?
From my code, the inference I draw is that Firefox is logging in and out very quickly because the logout time cannot be set any other way.
This is a sample of the total logins report Note user "Salmon"
