Problem:

The host system (MF ES IMS) has its timeout set to 30 minutes, the same as the Elink setting.  However, in many cases of user inactivity beyond 30 minutes, Elink accepts the user request and continues with the session. The following lines from server.log indicate that the user got the login screen "unexpectedly", but this is actually because the host has correctly timed out because the previous activity was more than 30 minutes ago:

2007/09/24 11:48:04 [0x1112] SSSessionMgr::Dispatch(3669): * Request completed for session 7Q0TFEj7wYcVmm8O, page JK0P30

2007/09/24 12:21:29 [0x1e1f] SSSession::hyperlink(7780): expecting UpdtHostScreen5273 but got DFS3649A218

2007/09/24 14:04:41 [0x1314] SSSessionMgr::Dispatch(3669): * Request completed for session 7Q0TFEj7wYcVmm8O, page JI0CMM

2007/09/24 14:46:48 [0x0405] SSSession::hyperlink(7780): expecting UpdtHostScreen5273 but got DFS3649A218

2007/09/24 14:56:09 [0x2122] SSSessionMgr::Dispatch(3669): * Request completed for session 7Q0TFEj7wYcVmm8O, page JL0P80

2007/09/24 15:28:59 [0x3b3c] SSSession::hyperlink(7780): expecting UpdtHostScreen5273 but got DFS3649A218

2007/09/24 18:51:26 [0x5758] SSSessionMgr::Dispatch(3669): * Request completed for session Qm6HtKOcGCeWa1FD, page JI0CMS

2007/09/24 19:42:27 [0x0e0f] SSSession::hyperlink(7780): expecting UpdtHostScreen5273 but got DFS3649A218

UpdtHostScreen5273 is the main menu to which the application often returns, while DFS3649A218 is the ES IMS logon screen.

The Elink Session timeout is set to the default 1800 seconds (the same as the ES IMS timeout).

Resolution:

By design, if "Force Disconnection" is not checked, EL Server does not terminate a session when the "timeout" limit is reached unless/until there is a request for a new session and there are no available free sessions (per the customer's license).  If the customer would like all inactive sessions to be terminated unconditionally upon reaching the "timeout" limit, then "Force Disconnection" should be checked.