Hi All,

I'm running a client / server app and have been testing with a few
colleagues...

This morning one my colleagues reported a screen full of warning dialogs
on the client PC saying:

'#1107 The session ID 5 is no longer present on the server.'

Does anyone have any experience with this and what's the nicest way to
trap the error / continue / possible reconnect?

Thanks,

Phil.

Screen shot example, so you can see what I'm going on about

See this for some info on handling it - your app should handle 1107
basically:

http://www.elevatesoft.com/forums?action=view&category=edb&id=edb_general&page=1&msg=11749#11749

and this is a good overview article of connections

http://www.elevatesoft.com/articles?action=view&category=edb&article=connections_disconnections_reconnections

Raul

On 10/17/2012 7:34 PM, Phil wrote:
> Hi All,
>
> I'm running a client / server app and have been testing with a few
> colleagues...
>
> This morning one my colleagues reported a screen full of warning dialogs
> on the client PC saying:
>
> '#1107 The session ID 5 is no longer present on the server.'
>
> Does anyone have any experience with this and what's the nicest way to
> trap the error / continue / possible reconnect?
>
> Thanks,
>
> Phil.

> See this for some info on handling it - your app should handle 1107
> basically:
>
> http://www.elevatesoft.com/forums?action=view&category=edb&id=edb_general&page=1&msg=11749#11749
>
>
> and this is a good overview article of connections
>
> http://www.elevatesoft.com/articles?action=view&category=edb&article=connections_disconnections_reconnections
>
>
> Raul

Thanks Raul,

Do you know how I can emulate the 2 scenarios for testing my handing for
both situations...

1. Where the remote session is *removed* from the ElevateDB Server
2. Where the remote session has simply been disconnected ?

Cheers,

Phil.

Phil,

> Do you know how I can emulate the 2 scenarios for testing my handing for
> both situations...
>
> 1. Where the remote session is *removed* from the ElevateDB Server
> 2. Where the remote session has simply been disconnected ?

Easiest would be to just disconnect or remove them straight from
edbserver window manually - when server is running just click on session
and you have 2 commands on left task pane: disconnect and remove.


Raul

> Phil,
>
>> Do you know how I can emulate the 2 scenarios for testing my handing for
>> both situations...
>>
>> 1. Where the remote session is *removed* from the ElevateDB Server
>> 2. Where the remote session has simply been disconnected ?
>
> Easiest would be to just disconnect or remove them straight from
> edbserver window manually - when server is running just click on session
> and you have 2 commands on left task pane: disconnect and remove.
>
>
> Raul

Hi Raul, I'm using my own server program as oppose the ELevateDB Server,
so I was wondering what properties to set to emulate them.

I'm guessing I can just add the options temporarily to emulate it, but
just wondering what I would be setting specifically.

Cheers,

Phil.

OK I've got that part working using the Exception Handler and trapping
the error codes I needed to in the client program, works well.

Now my issue is, on the Server program if I try to STOP the engine
(ServerEngine->Active = false) while there are remote connected users
the server program freezes.

So I tried having it loop through the configuration.serversessions and
using the "REMOVE SERVER SESSION X" prior to closing the engine, but it
doesn't appear to remove them and it still freezes... (strange).

Strange, because if I run the "REMOVE SERVER SESSION X" from say the
ElevateDB Manager then I can see the remote sessions dropping away in
the TListView control that lists the sessions in my Server app.

Any ideas? Is there not a simple way to CLOSE the server and not have it
hang if there are connected remote sessions? I must be doing something
wrong prior to closing down.

Thanks,

PHil.

All good, I ended up scrapping the SQL ("REMOVE SERVER SESSION X") and
used the...

ServerEngine->RemoveServerSession(X); // X = sessionID

Which gave the desired result.

Thanks,

Phil.

Phil,

<< This morning one my colleagues reported a screen full of warning dialogs
on the client PC saying: >>

Are you using pinging with the remote sessions on the clients ?
(TEDBSession.RemotePing=True).  If not, then you should definitely enable
it, otherwise you could run into situations where the EDB Server will remove
disconnected (dead) sessions once they hit the dead session expiration time
limit.  See the technical article that Raul linked to regarding how to
handle this:

http://www.elevatesoft.com/articles?action=view&category=edb&article=connections_disconnections_reconnections

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

> Are you using pinging with the remote sessions on the clients ?
> (TEDBSession.RemotePing=True).  If not, then you should definitely
> enable it, otherwise you could run into situations where the EDB Server
> will remove disconnected (dead) sessions once they hit the dead session
> expiration time limit.  See the technical article that Raul linked to
> regarding how to handle this:
>
> http://www.elevatesoft.com/articles?action=view&category=edb&article=connections_disconnections_reconnections

Thanks Tim,

Yep remote pinging was always true and its all been running problem free
since I put in the error trapping of remote sessions as suggested by
your excellent post here.
http://www.elevatesoft.com/forums?action=view&category=edb&id=edb_general&page=1&msg=11749#11749

Cheers mate,

Phil.