Hi folks,
Do you know where these client connection details are stored?
Thank you for your support!
...Alex
*This post is locked for comments
Matt,
Indeed, the HQEventLog table doesn't record (not even temporarily) any client connections whatsoever. It just records the messages exchanged by the HQ Server and the HQ Client -darn!
So, the only way, I think. I am able to trace possible hung connections is by running NETSTAT against the HQ server on the HQ server process listening port such as netstat -an | find "34200" where 34200 is the listening port.
Cheers!
...Alex
Matt,
These connections were indeed hung :(
Since we have the HQ Server running on the server at the console level, there are no eyes watching over, that's why I'd like to query the database to find out about them.
Once I know which table and the query, I can schedule the query to run every 1 hour to look for those hung connection and take action.
I will try to come up with the query on my lab and share with you if I am successful.
Thanks for following up :)
...Alex
That info doesn't get recorded to a log file. By looking at your picture, it seems like you have the same machine that timed out the first attempt or lost network connection, then connected again. I haven't been able to find a way to automatically release those hung connections, other than monitor the server window and delete duplicate entries, or those that have been there too long.
Matt,
The HQEventLog table doesn’t seem to have Address, State and the “Client Properties” fields, can you think of another table or log file on the file system or how would you query it to get these details?
Thanks,
…Alex
hqeventlog
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,888 Super User 2024 Season 2
Martin Dráb 229,247 Most Valuable Professional
nmaenpaa 101,156