Diese Seite mit anderen teilen ...

Informationen zum Thema:
Forum:
WinDev Forum
Beiträge im Thema:
5
Erster Beitrag:
vor 4 Monaten
Letzter Beitrag:
vor 4 Monaten
Beteiligte Autoren:
DerekT, Fabrice Harari, Peter Holemans, Jan de Bruin, Noel Tanti

HFSql Center Connection Information

Startbeitrag von Noel Tanti am 11.08.2017 08:08

Hi All

in the screen there is no information of when the connection was last used or when it was created.

I am having servers with hundreds of connections, some connections are obviously dead, and cannot know which are the ones in use so that I can remove the others.

1. does this date/time detail exist somewhere in the hfsql center
2. what can I do on the software side to clear ,dead. connections or make sure that when the user exit the applications the connection is closed?

Thanks & regards
Noel

Antworten:

Maybe Hcloseconnection?

von Jan de Bruin - am 11.08.2017 11:42
Hi Jan,

Noel is talking about the HF Control Center 'Connections' tab on an HFSQL C/S...
This is a shortcoming/bug that has always been around.

In short: In the grid listing the actual connections, you have no clue if it is an active connection or a dead one.
There's no date, time, last activity timestamp or whatever to identify that.

We still have a WD application running for one of our clients that connects to a cloud HFSQL C/S.
Most of the times when the client app has to reconnect to the HFSQL C/S (happens a lot when the customer is using a WiFi connection) the old connection will be dead but it will still be listed in the Control Center as an active connection and a new one will be created and added into this list. As of that moment you have no clue which one has become obsolete and thus which one you can kill. Simply because the data to analyse it is not there...

I always have known this as an issue but it didn't seem to affect performance so it wasn't a major deal... Might be I even raised a support call for it 7 years ago or so (Not sure though)... Guess the other 9xx something gadgets had as usual more priority instead of fixing stuff.

Cheers,

Peter Holemans

von Peter Holemans - am 11.08.2017 12:43
Hi Noel

there was an example doing just that in the last LST. I cannot give it to you for legal/copyright reason, but I can explain the principal of the thing:

- from your program or a utility connected to the same DB, you send a broacast message to all clients using HSendMessageToClient
- of course, it means that your prgram must be able to receive such message (and do nothing)

The neat trick is that when the HF server sends the broadcast message to each open connexion, it also CLOSES each connexion that does not 'answer', ie is dead.

And hop, it's done.

Best regards

von Fabrice Harari - am 11.08.2017 13:12
As you say 'neat trick' if somewhat bizarre.

PCS at their very eccentric best:rolleyes:

von DerekT - am 11.08.2017 13:35
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.