If you change the value of a property in a Connection object after it has been instantiated, the Connection object might not recognize the change, depending on the session model as described in the following table.

Table 1. Relationship between Connection object properties and session model
If this Connection object property is updated . . . Then the update is . . .
Session-managed Session-free 
PROGRESS.Session.ConnectionLifetime
 Not applicable Ignored 
PROGRESS.Session.ConnectionTimeout
 Recognized once pick list is refreshed Recognized once pick list is refreshed 
PROGRESS.Session.IdleConnectionTimeout
Not applicable Ignored 
PROGRESS.Session.InitialConnections
Not applicable Ignored 
PROGRESS.Session.MaxConnections
Not applicable Ignored 
PROGRESS.Session.MinConnections
Not applicable Ignored 
PROGRESS.Session.NoHostVerify
Ignored Ignored 
PROGRESS.Session.NsClientMaxPort
 Not applicable Ignored 
PROGRESS.Session.NsClientMinPort
 Not applicable Ignored 
PROGRESS.Session.NsClientPicklistExpiration
 Not applicable Recognized once pick list is refreshed 
PROGRESS.Session.NsClientPicklistSize
 Not applicable Recognized when pick list is refreshed 
PROGRESS.Session.NsClientPortRetry
 Not applicable Ignored 
PROGRESS.Session.NsClientPortRetryInterval
 Not applicable Ignored 
PROGRESS.Session.ProxyHost
Ignored Ignored 
PROGRESS.Session.ProxyPassword
Ignored Ignored 
PROGRESS.Session.ProxyPort
Ignored Ignored 
PROGRESS.Session.ProxyUserId
Ignored Ignored 
PROGRESS.Session.RequestWaitTimeout
Not applicable Recognized for new requests 
PROGRESS.Session.TcpKeepAliveInterval
Recognized Recognized for new requests