Question

If a machine has a temporary disconnect to the network, with LF Client open, will a new Session ID be created on reconnect?

Audit Trail Laserfiche Version 9 Administration

Updated December 20, 2013

asked on December 19, 2013

I was wondering what happens if a machine gets disconnected from the network for a temporary (half second maybe) amount of time. If the user has LF Client open, when this happens, would the users session have a new session ID?

1 0

Answer

APPROVED ANSWER SELECTED ANSWER

replied on December 19, 2013

Each session has a unique session id, so the question boils down to whether a new session is created. For such a short network disruption, I wouldn't expect either end of the connection (client or server) to notice; if there is active communication at the moment of disruption, TCP should handle retransmitting any lost packets. The longer the two ends are unable to communicate, the more likely it becomes that the server will assume the client is gone (and log them out) or the client will discover a problem and try to reconnect.

All that said, why are you interested in session ids?

1 0

replied on December 19, 2013

I was wondering because of a document lock and if a user gets disconnected, if a new session ID is created and/or the lock remains from the previous session? We have a client having trouble with opening a file all day and at the end of the day it says the entry is locked and I am trying to make sense of the audit trail and figuring out if the user logged out and logged back in or whatever else the audit trail is indicating. We have not found a reason for the entry to be locked as no other user is accessing it during the times the user in question accesses the document

0 0

Replies

replied on December 19, 2013

Yes, entry locks are tied to a session and if you see a new session id in Audit Trail then that suggests that the user was reconnected. You might want to look into the login and logout events for those sessions; that the document was reported as locked suggests that maybe the first session was never really terminated.

Regular write locks are really only necessary while there are unsaved changes in the client. Maybe your users have an unusual use case, but I would expect users would save their changes fairly regularly. If they really need to hold a lock all day you might encourage them to check out the document, since those locks persist over sessions.

0 0

replied on December 20, 2013

Hi Brian,

Can a column be added "connection ID" in the entry locks node?

0 0

View 1 previous reply

replied on December 20, 2013 • Show version history

Brian,

The reason for Ranzu's request is that we had a user that was closing LF Client while having a document open and then opening up LF Client again and then saving the document. (xlsx file). We were hoping for this information to be present so when you look at the administration console, you can see that the active sessions of the user is not the same session(s) the user locked the document with. This would've been more helpful to our diagnosing of the issue.

Alternatively, having this capability would show us which machine/session a user is using to open a specific document. Say, they have a laptop or an iPad with an entry open and then a second or third machine open, how do we know which machine has the entry locked or not. It would be useful to know which machine is in use of that document so they can make sure they have saved or not saved the latest version to laserfiche without wondering if/where the document is open (assuming they didnt forget they had the document open on the other machine)

I am sure someone else can come up with a better use-case for this feature, as it would allow for much more precise control/overview of the current happenings inside a repository

0 0

replied on December 20, 2013 • Show version history

I understand why it would be useful for troubleshooting this scenario. But it seems to me that the better approach would be to prevent the problem rather than make it easier for an administrator to diagnose when a user is inconvenienced by it. Do you really have users begin modifications on one device, leave those changes unsaved, open the same document for editing on another device, and then they don't know which device they began the edit on? I don't understand how this can happen in practice, but maybe you can change their processes to prevent it.

0 0

replied on December 20, 2013

Brian,

We actually had a client open a document and then close laserfiche client, then open the client again before then saving to laserfiche the original opened document (sometimes an hour or two later).

We have a bit of difficulty showing whether they closed and re-opened the document or just kept it open and was unable to save the document because it was locked by himself from another session.

0 0

replied on December 20, 2013

The Sessions node in LFAdmin Console lists the username, application and computer for each connection.

0 0

replied on December 20, 2013

yes, but not the associated locked files to that session. And the Entry Locks node does not show the session ID associated with that lock

0 0

replied on December 20, 2013

Right, but the goal is for the user to figure out what devices he may have left things unsaved on, isn't it? So it is more useful to know where you have a session open other than the current machine (potentially more than just the one file you got an "entry locked" error on and potentially keeping you from logging in at all if you hit the concurrent session limit) than figuring out the session ID associated with a particular lock ID.

0 0

You are not allowed to follow up in this post.

Question

Question

If a machine has a temporary disconnect to the network, with LF Client open, will a new Session ID be created on reconnect?

Answer

Replies

Sign in to reply to this post.