connection issues

Hi all, we are having issues with connections not being released timeously from the database. We are running IDS 10 FC5 on an HP/UX box. Users connect to the database over ODBC or via the informix native drivers on to an onsoctpc connection to the database. We either run into a problem with too many connections (memory constraints) or, since some of the sessions can use a large number of scan threads and the threads are not released after the transaction has completed, we run out of threads and the database asserts. We have experimented on the client side by turning on and off connection pooling but to little avail. There are no instructions in sqlhosts or the onconfig file to modify the connection behaviour. Does anyone have any suggestions as to how we can resolve this problem? regards Mark

Mark wrote: > Hi all, > > we are having issues with connections not being released timeously from the > database. > Sounds like the clients are Windows apps. Windows is notorious for not releasing TCP connections. One thing, as you have already tried, it to disable connection pooling for the connections. The only other thing you can do, for applications written in-house, is to be certain to disconnect from the database within the code under ALL circumstances even in the event of an exit through the red X in the app's window frame. You should register a function with the Windows exit stack that will check whether there is still an active connection to the database and shut it down. Windows apps, especially MS developed apps like Excell, do not do this and there's not much you can do about it. On the server side, you can also try setting a keep-alive period to auto retire idle sessions. Art S. Kagel Oninit > We are running IDS 10 FC5 on an HP/UX box. > > Users connect to the database over ODBC or via the informix native drivers > on to an onsoctpc connection to the database. > > We either run into a problem with too many connections (memory constraints) > or, since some of the sessions can use a large number of scan threads and > the threads are not released after the transaction has completed, we run out > of threads and the database asserts. > > We have experimented on the client side by turning on and off connection > pooling but to little avail. > > There are no instructions in sqlhosts or the onconfig file to modify the > connection behaviour. > > Does anyone have any suggestions as to how we can resolve this problem? > > regards > > Mark ================================================================================ =========== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.oninit.com/home/disclaimer.php ================================================================================ ===========