Is there a limit in connections opened per second for the ODBC Driver?
484394Feb 8 2006 — edited Feb 8 2006Hi you all.
I have a thread intensive windows service written in Visual C++ for a communicacions app.
There is a mother thread which launches child threads each of which open a new connection to Oracle by means of the ODBC Driver.
The child threads are created and die, buy sometimes a big amount of them can be created at the same time (about 200 threads when a massive alert is sent to the remote client apps) which mean that about 200 connections are opened against the driver in an instant using the same user/pass.
Mi problem is that when this happens some threads are frozen in the Open function of the database connection.
I tried to write a bit of code to test it (one loop which launched threads which just opened connections to the database and waited in an infinite loop to keep everything opened) and the problem persisted. But as this time it was a desktop app (not a winservice) an Oracle ODBC Driver Connect dialog showed asking for Service Name, User Name and Password.
I tested the same code against a SQLServer driver and the app had no problem in launching all the threads.
So now comes the question ¿is there a limit in the driver for the number of connections per second?
I am using Oracle's Driver version 10.01.00.31 and the database is an Oracle 10gR1, and the service is written in Visual C++ (Visual Studio 2003).
The database is not owned by us, so we cannot modify any parameters.
I have checked the SESSIONS_PER_USER in the profile we have been assigned and it is UNLIMITED.
Thank you in advance and excuse my poor English.