I have a client with disconnected sessions that just sit there and never get cleaned up or not for quite some time. They show disconnected (IP ADDRESS) and sit there for an hour or more any reason why?

Most of the timeouts are low
connection timeout: 60
Dead session cleanup interval: 5
Dead session expiration: 5

This is the log for an IP address that just showed as disconnected. The IP can have multiple users but this is what it showed if it helps.


16/01/2017 10:47:11 AM Connection accepted [Client Version: 4.36 User Name:  Address: 144.139.73.216 Encrypted: No Thread: 3528 Session: 1]
16/01/2017 10:47:11 AM Login [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 3528 Session: 1]
16/01/2017 10:47:12 AM Connection closed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 3528 Session: 1]
16/01/2017 10:47:12 AM Logout [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 3528 Session: 1]
16/01/2017 10:47:20 AM Connection accepted [Client Version: 4.36 User Name:  Address: 144.139.73.216 Encrypted: No Thread: 3528 Session: 1]
16/01/2017 10:47:20 AM Login [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 3528 Session: 1]
16/01/2017 10:47:47 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:47:47 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:48:58 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:48:58 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:49:13 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:49:14 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:49:30 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:49:30 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:49:54 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:49:54 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:50:23 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:50:23 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:50:27 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:50:27 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:50:43 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:50:43 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:50:46 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:50:46 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:51:23 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:51:24 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:51:55 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:51:56 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:52:18 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:52:19 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:17 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:18 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:22 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:22 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:27 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:27 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:30 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:30 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:30 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:30 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:31 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:31 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:40 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:40 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:40 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:40 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:51 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 10:53:52 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3528 Session: 1]
16/01/2017 10:54:14 AM Connection accepted [Client Version: 4.36 User Name:  Address: 144.139.73.216 Encrypted: No Thread: 2368 Session: 6]
16/01/2017 10:54:14 AM Login [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 2368 Session: 6]
16/01/2017 10:54:15 AM Connection closed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 2368 Session: 6]
16/01/2017 10:54:15 AM Logout [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 2368 Session: 6]
16/01/2017 10:54:16 AM Connection accepted [Client Version: 4.36 User Name:  Address: 144.139.73.216 Encrypted: No Thread: 3276 Session: 6]
16/01/2017 10:54:16 AM Login [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 3276 Session: 6]
16/01/2017 10:54:46 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3276 Session: 6]
16/01/2017 10:54:46 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 3276 Session: 6]
16/01/2017 10:58:30 AM Connection accepted [Client Version: 4.36 User Name:  Address: 144.139.73.216 Encrypted: No Thread: 2456 Session: 18]
16/01/2017 10:58:30 AM Login [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 2456 Session: 18]
16/01/2017 10:58:31 AM Connection closed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 2456 Session: 18]
16/01/2017 10:58:31 AM Logout [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 2456 Session: 18]
16/01/2017 10:58:31 AM Connection accepted [Client Version: 4.36 User Name:  Address: 144.139.73.216 Encrypted: No Thread: 2388 Session: 18]
16/01/2017 10:58:31 AM Login [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 2388 Session: 18]
16/01/2017 10:59:00 AM Restricted transaction started [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 2388 Session: 18]
16/01/2017 10:59:01 AM Transaction committed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_COMMITTRANS Thread: 2388 Session: 18]
16/01/2017 11:02:32 AM [ERROR] Engine error [DBISAM Engine Error # 10229 Transaction cannot lock the database 'ClockOnData'] [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3528 Session: 1]
16/01/2017 11:02:32 AM Connection closed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 3528 Session: 1]
16/01/2017 11:02:43 AM [WARNING] Dead session removed [Client Last User Name: admin Last Address: 144.139.73.216 Thread: 0 Session: 1]
16/01/2017 11:03:58 AM [ERROR] Engine error [DBISAM Engine Error # 10229 Transaction cannot lock the database 'ClockOnData'] [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Request: REQUEST_STARTTRANS Thread: 3276 Session: 6]
16/01/2017 11:03:58 AM Connection closed [Client Version: 4.36 User Name: admin Address: 144.139.73.216 Encrypted: No Thread: 3276 Session: 6]

On 1/15/2017 8:01 PM, Graham Mylne wrote:
> I have a client with disconnected sessions that just sit there and never get cleaned up or not for quite some time. They show disconnected (IP ADDRESS) and sit there for an hour or more any reason why?
> Most of the timeouts are low
> connection timeout: 60
> Dead session cleanup interval: 5
> Dead session expiration: 5

What is version of the server (4.36 or something different?)

There were some fixes to dead session removal but they appear to be
fixed by 4.36.

There is one more fix in 4.38 b2 but that might not affect you
(http://www.elevatesoft.com/incident?action=viewaddr&category=dbisam&release=4.38&incident=4021)
but not s

Assuming you use session pinging in your app sessions should remain
connected even if there is no user activity.

In that case connection timeout itself might not matter unless there is
an actual network issue or similar  (i.e. user puts pc to sleep or
disconnect wifi etc thus killing the connection on their side).

Once disconnected though the server should check for dead session every
5 seconds and then should remove them once they are 5 seconds old -
depending on timings the session could hence remain in disconnected
state for 10 seconds or .


> This is the log for an IP address that just showed as disconnected. The IP can have multiple users but this is what it showed if it helps.
>

Looking at session 1 the process did work : Session 1 was disconnected
at 11:02:32 and removed 11:02:43 as configured

Session 6 did disconnect at 10:54:15 but then reconnected at 10:54:16 so
dead session logic does not apply.

Similarly Session 18 closed at 10:58:31 and reconnected same second.

Session 6 did disconnect at 11:03:58 but that is last entry so not sure
if you saw session 6 as disconnected or something else.

Raul

Its build 4.36 build 3. Its otherwise working fine but these sometimes hand around for an hour or more, ill have to check how long. But is this reasonable and they will clean up or is something else wrong here?

On 1/16/2017 8:42 PM, Graham Mylne wrote:
> Its build 4.36 build 3. Its otherwise working fine but these sometimes hand around for an hour or more, ill have to check how long. But is this reasonable and they will clean up or is something else wrong here?

Based on the settings you have IMHO disconnected sessions should not
hang around for an hour - you have very aggressive session removal settings.

Ideally if you could figure out the session ID and then correlate
sessions activities with the log it would - tricky in this case if
multiple users originate from same id and same (admin) login is in use.

Another option would be to upgrade to latest dbisam and see if issue
persists - however since everything works fine i'd try to figure this
out with current version first.

Raul

Dont think i could back trace all the operations and yes there are multiple users on the same public IP address so narrowing it down is a bit tricky.

Graham,

<< I have a client with disconnected sessions that just sit there and never get cleaned up or not for quite some time. They show disconnected (IP ADDRESS) and sit there for an hour or more any reason why? >.

Are you seeing any errors in the server log related to the DBISAM Database Server *not* being able to remove a dead session ?  That would indicate that the DBISAM Database Server is using the dead session settings properly, but cannot remove the session for other reasons.

Tim Young
Elevate Software
www.elevatesoft.com

Nothing regarding dead sessions not being to remove any sessions.

Our biggest hosted server with more connections does not seem to get this issue, but this customer does consistently. Are there any written temp files or something else that the server might be locking that could cause the clean up process to fail?

Graham,

<< Nothing regarding dead sessions not being to remove any sessions. >>

Hmm, you should definitely see an error in there if the DBISAM Database Server cannot remove a dead session.  In addition, there *are* logged events in the server log for dead session removal events, so at least some of the dead sessions are getting removed and the dead session removal process is working.

Also, you mention that the dead sessions hang around for an hour or more.  Does this mean that you are eventually seeing them get removed by the server, or are they never removed ?

Tim Young
Elevate Software
www.elevatesoft.com

They do seem like they are being removed after an hour or so, i dont think from memory they are hanging around longer than that. I have changed the dead session clean up times to be 10 seconds to timeout and 30seconds on clean up, in case there is a timing issue there.

The issue does not seem to be across all of our customers just the larger ones we have notices this and some get quite a few of these too.