[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Secondary broker logins (increasing maximum number of connections on the fly)

Status
Not open for further replies.
D

dbeavon

Guest
Thanks Ruanne, It would be nice if the disabling of pooling could be done in an app-specific way without messing with the driver in the ODBC administration. Simply adding "Pooling=false" to a connection string would be wonderful for troubleshooting purposes. (And it would also be helpful to use that within services that don't need any pooling). While searching google, I saw a lot references to the configuring of pooling in connection strings. But the context wasn't normally related to ODBC connections. It was usually a managed provider of some kind. There are very few ODBC providers that seem to support the configuration of pooling via connection strings . The ReleaseObjectPool is something we can use in a pinch. It is pretty ugly to do on a regular basis.

Continue reading...
 
Status
Not open for further replies.
Top