Unbound connections
- Last Updated: January 16, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
You can request that a bound connection become unbound by setting the
SERVER-CONNECTION-BOUND-REQUEST attribute on the
SESSION handle to FALSE. However, the connection
only becomes unbound as long as there are no remote persistent procedures still active
in the PAS for OpenEdge session.
Once a connection transitions from the bound to the unbound state, the PAS for OpenEdge session can handle the next request sent by any connected client, whether it is session-managed or session-free. Conversely, the next request sent by the client on the previously bound connection can be handled by any available PAS for OpenEdge session.
If remote persistent procedures are active on a bound connection, setting the
SERVER-CONNECTION-BOUND-REQUEST attribute to FALSE
has no effect until all remote persistent procedures in the bound session are explicitly
deleted. When all remote persistent procedures are deleted, the connection either
remains in the bound state or becomes unbound depending on the last setting of the
SERVER-CONNECTION-BOUND-REQUEST attribute.