Inhaltsverzeichnis anzeigen | ![]() |
Shows the current status of the database connections (active, passive, crashed, that is, still open)
Shown in the header area
Free Connections |
Shows the number of free connections The number after the / indicates the number of vacant query connections |
Used Connections |
Shows the number of used connections The number after the / indicates the number of occupied query connections |
Connection display
The used and available connections are displayed.
Time |
The last action and time of the connection is displayed |
Requested by |
Information about the request of the connection is shown |
Note: Once the efficiency of the connection pool crosses a certain limit, queries are sent to a waiting loop: "The system is working at full capacity . Please be patient..." Apodosis "(If page doesn't create automatically, please click here)".
This should prevent a sort of snowball effect in criticial situations. The database is overloaded, the connection pool opens new connections, this slows down the database even more, etc.
The threshold is defined in the config.xml - under the keyword 'DBMaxConnections'. If 90% of the value configured here is readched, the named warning is displayed. This value should be somewhat higher than half of the maximum number of simultaneously active users (e.g. for 100 users, DBMaxConnections=60). The default value is 100.
The value DBQueryPoolSize in the config.xml specifies how many connections must at least be made available to guarantee fast response times (a value of 15 would be ideal here).