Forum Discussion

LukeMih's avatar
LukeMih
Level 3
11 years ago

Enterprise Vault for Lotus Domino Sessions

I'd just like to pose the question.  How many established sessions does a EVDG establish and leave open on a per provisioned user.  For instance, 1000 users provisioned, 660 EVDG sessions to the prim...
Enterprise Vault
Error messages
Information Governance
Troubleshooting
Windows Server (2003-2008)
  • Arjun_Shelke's avatar
    Arjun_Shelke
    11 years ago

    Ok, so for example if you have 1000 EV enabled users accessing thier mailfiles and symultaneously they are accessing archived items and EV is also archiving items from mailfiles at the same time then it would look like:

    Notes users mailfile access: 1000 sessions.

    Notes users accessing archived items: EVDG to Mail Domino - 1000 Sessions.

    EV Archiving Task: Trawling mailfiles, using 10 sessions at a time.

    Total TCP/IP sessions used = 2010 sessions.

    Is this correct? If yes, then the EVDG sessions to Mail Domino would be 1010 at that time. This should be the theoritical boundary to the max sessions. But we forget to add EV Domino Provisioning Task which runs twice a day to update few things in users mailfile. So this task will also eat some sessions, not sure how many sessions will be used at a time by this task.

    Looking at the scenario, I feel like idle sessions are not killed in time?

    I have not seen this behaviour ever, not sure if you can change the TCP IP port for EVDG sessions. I think the sessions are not killed properly, when user retrieves archived item and closes the open note window, the EVDG session for that item/mailfile should be killed or kept idle for some time for next retrieval and then killed if not used.

LukeMih's avatar
LukeMih
Level 3
11 years ago

I think I have instituted a workaround at least for the problem I was seeing when the server would throw console errors, recycle existing connections and reset the connection limit to lower numbers.  The setting that I changed was the notes.ini parameter Server_Session_Timeout which was by default 240 minutes.  I reset this to 30 minutes and have noticed that the session count, so far today is reasonable for our workload.

The console command for showing that statistics:

show stat net.tcpip.sessions.peak

Currently: NET.TCPIP.Sessions.Peak = 638


Previously: NET.TCPIP.Sessions.Peak = 3946

 

I have a suspicion that the timeout parameter being 4 hours by default is a bit high if the applications using domino are relying on the domino server to terminate the idle connections in a 1000+ user environment.  However, the strange part I see is that we almost never see more than 140 notes/inotes users signed into this domino server.

 

LM