Why does the ODBC-ODBC Bridge HTTP server statistics page show active threads when there are no connections?

The Easysoft ODBC-ODBC Bridge HTTP server statistics page shows you both current and historical ODBC-ODBC Bridge server activity. The ODBC-ODBC Bridge server registers a new active connection when a client successfully connects and a thread (or process) starts up to handle the ODBC connection. The server does not deregister the connection (as far as the statistics are concerned) immediately after the client disconnects. The server searches for disconnected threads or processes when there have been no incoming connections for a period of 5 seconds. This gives priority to incoming connections. This also affects the peak concurrent connection count. For example, if you write a program that connects and disconnects in one second and repeats this process every 3 seconds, the active connections and peak concurrent connections will increase until your program stops.

There is one situation in which this is not the case. If you set MaxClientConnect or MaxThreadCount to a value other than 0 to limit the connections, the Server checks for terminating threads or processes every time a connection is made, so the active and concurrent counts will always be up to date immediately after an ODBC connection from a client.

This does not affect licensing. If you have a license limited to n concurrent connections, the server does not use the active connections statistic to decide whether you can connect or not.