Pending Connection Time (-PendConnTime)
- Last Updated: November 12, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
Use Pending Connection Time (-PendConnTime) to prevent connection errors
caused by network problems.
| Operating system and syntax | UNIX / Windows |
-PendConnTime
n
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| Database Server | — | — | — | 0 |
- n
- Time, in seconds, allowed the client to connect to a server.
When a client attempts to connect to an OpenEdge database, the RDBMS assumes that if the client can reach the broker, it can also reach the server. Network problems or incorrect configuration of network devices can prevent the client from reaching the server. In such an instance, the broker, unaware that the client's connection failed, continues to increment its count of connected users. To prevent this problem, OpenEdge brokers use a "reservation" count on each server and they increment this count whenever they redirect a client to that server.
When -PendConnTime is used, the servers examine the timestamp on the
latest reservation and, if the Pending Connection Time period has elapsed, the broker
assumes that the client has failed to connect. The broker then clears the reservation,
making the server available for new clients.
The Pending Connection Time (-PendConnTime) parameter may
be modified while your database is online using PROMON or through the _DbParams VST. This
change will only take effect on the primary broker and any newly spawned servers. Online
changes to existing servers and secondary brokers will require a restart.