Greetings,

We're seeing a lot of these errors in the LogEvents on a recently deployed remote server.  I'm not sure where to start looking first.  First, can anyone tell me which side is the culprit - server or client, or a combination of both?  I'm also assuming we should be addressing these errors rather than ignoring them.

Thanks,
Al

On 6/24/2014 11:07 AM, Alan Craker wrote:
> We're seeing a lot of these errors in the LogEvents on a recently deployed remote server.  I'm not sure where to start looking first.  First, can anyone tell me which side is the culprit - server or client, or a combination of both?  I'm also assuming we should be addressing these errors rather than ignoring them.

its likely due to server removing expires sessions (or what it hitnks
are expired). Are you using remote pinging in the session to ensure
session heartbeat ?

This older thread should give you a start on the issue

www.elevatesoft.com/forums?action=view&category=edb&id=edb_general&page=1&msg=15117

Definitely read the linked tech article  : Connections, Disconnections,
and Reconnections
(http://www.elevatesoft.com/articles?action=view&category=edb&article=connections_disconnections_reconnections)

Raul

Alan


Looking at the manual

EDB_ERROR_SESSIONNOTFOUND (1107)

The session ID <SessionID> is no longer present on the
serverThis error is raised whenever a remote session
attempts to reconnect to a session that has already
been designated as a dead session and removed by the
ElevateDB Server. This can occur when a session is
inactive for a long period of time, or when the
ElevateDB Server has been stopped and then restarted

suggests to me that its clients not doing very much (could be lost network connections as well). The solution is probably ServerSessionTimeout and RemotePing. The actual values will depend on your circumstances. If you search these newsgroups you'll find some suggestions (I use f/s rather than c/s so can't help there).

If you still get the error after setting these then I'd suspect network connections dropping out. That's more or less easily resolved depending on wether its LAN or WAN.


Roy Lambert