Hi

Is this a general problem or my ignorance ... bet it is the later.

I have a EDB server running on a "cloud server".  If I'm working with
EDBMgr and leave for a while - e.g. do some Delphi development or make a
cuppa tea - when I come back I find that EDBMgr has timed out.

My application does not time out - it has remote pinging and I've put
code in the various events as recommended in this forum.  So all is well
there.

It is just a frustration thing for me, more serious for my colleague
would does the technical support for our users and is "forever having to
bash in his password to reconnect".

The message that we are getting is:-

"The connection to the ElevateDB Server has been interrupted or timed
out and needs to be re-connected.  Would you like to continue with the
connection ?"

.... plus another one you have to click through which I haven't recorded.

It seems to me that EDBMgr isn't pinging the server, but I can't see a
way to make it do that.

Below are what I think are the relevant entries in the server .ini file.

Cheers

Jeff
--
Server Name=EDBSRVR
Server Description=ElevateDB Server
Server Run Jobs=1
Server Job Category=
Server Address=
Server Port=12010
Server Thread Cache Size=10
Server Encrypted Only=0
Server Session Timeout=180
Server Dead Session Interval=30
Server Dead Session Expiration=300
Server Maximum Dead Sessions=64

On 22/05/2015 2:00 p.m., Jeff Cook wrote:
> Hi
>
> Is this a general problem or my ignorance ... bet it is the later.
>
Further to my previous post ...

Using 2.18 Build 4

The following entries are in the EDBMgr.ini file:-

[Session_Cloud Session]
Creation Order=4
Name=Cloud Session
Description=
Type=1
Character Set=1
Force Buffer Flush=0
Keep Tables Open=0
Row Lock Protocol=0
Row Lock Retry Count=15
Row Lock Wait Time=100
Row Change Detection=0
Login User=XXXXXXXXXXX
Login Password=XXXXXXXXXXXXXX
Progress Interval=1000
Configuration In Memory=0
Configuration Folder=
Configuration Name=EDBConfig
Large File Support=0
Standard NULL Behavior=1
Show Database Catalog Information=1
Cache Modules=0
Maximum Log File Size=1048576
Log Information Events=1
Log Warning Events=1
Log Error Events=1
Temporary Tables Path=C:\Users\JEFFCO~1\AppData\Local\Temp\
Catalog Name=EDBDatabase
Configuration File Extension=.EDBCfg
Lock Files Extension=.EDBLck
Log File Extension=.EDBLog
Backup Files Extension=.EDBBkp
Update Files Extension=.EDBUpd
Catalog Files Extension=.EDBCat
Table Files Extension=.EDBTbl
Table Index Files Extension=.EDBIdx
Table BLOB Files Extension=.EDBBlb
Table Publish Files Extension=.EDBPbl
Local Signature=edb_signature
Local Encryption Password=elevatesoft
Remote Compression=9
Remote Host=
Remote Address=999.999.999.999
Remote Port=12010
Remote Service=
Remote Signature=xxxxxxxxxx
Remote Encryption=0
Remote Encryption Password=xxxxxxx
Remote Timeout=180
Remote Ping=1
Remote Ping Interval=60

Jeff


Looking at the parameters you've posted I think remote pinging is enabled (its on the Remote page of the session editor form). I've never used EDBManager with long enough pauses in work to have it time out so I don't know if it actually works.

Can you try a test on something that's not connected to the cloud to see what happens? I'll have a go here and just leave a connection up whilst I take my wife to the dentist.

Roy Lambert

3 or so hours later it all seems fine. I'm going to try without the login information in EDBManager.

Roy Lambert

Roy,

> 3 or so hours later it all seems fine. I'm going to try without the login information in EDBManager.

Hopefully your wife is at home again from the dentist.

Uli

Uli


>Hopefully your wife is at home again from the dentist.

Since she doesn't drive so I have to chauffeur her - if I'm back - she's back

Roy

ps even without login credentials a few hours later it still hasn't timed out

Jeff


I can't get it to time out here on my LAN with remote pinging set. It may be that the ping isn't getting through.

Roy Lambert

On 23/05/2015 2:33 a.m., Roy Lambert wrote:
> Jeff
>
>
> I can't get it to time out here on my LAN with remote pinging set. It may be that the ping isn't getting through.
>
> Roy Lambert
>

Hi Roy

Thanks for your input.  Your testing is similar to mine, but doesn't
involve the dentist

I have tried using ping from the Windoze command line and that times out
too. I'll have to follow that one up ... after the weekend - possibly a
set up on the cloud server.

Presumably, "ping" in the ElevateDB sense isn't the same as a windows
ping.  In our DBISAM3 app we had a timer that fired of
"Session.GetRemoteDateTime" periodically and that was our "ping".

Cheers

Jeff

.... And I just realised that the same happens with a server on my LAN.

Jeff Cook wrote:

> ... And I just realised that the same happens with a server on my LAN.

It sounds as if your firewall, router or whatever is blocking pings.