ADO error 0x80040e37

I have a C++ program that accesses SQL database using ADO.
Everything runs fine on the manual test but when I do a stress test after running for while I get the "out of database connections" in my logs.
I checked into my code and found that the SQL statement execution command returns a "0x80040e37" error.
I read that this could be related to CA certifications etc. but my question is how does this work when I do manual tests and why does it run fine for a while on stress test and then start throwing these errors.
:ehh:
Please advice.

how many simultaneous connections are you, or others, making against the
datasource?

could use a little more info. most datasources have a limit
on the number of connections.

j

There might be around 24 users connected during a stress test and it runs fine for 2-3 hours. Is there any way to check how many connections are being made to the datasource.
Where do we set the limit to the number of connections.

Thanks. :ehh:

must admit i do not know. not aware of what particular db you are using but can tell you i experienced sybase, an enterprise db, not being able to handle somewhere in the vicinity of 30 connections simultaneously.

this is a sticky situation - usually solved setting up a mechanism to testing if a connection is available - if so submit the sql, if not go to sleep for a time
and try again. perhaps set a limit of retries and trigger alarms in some way if it is surpassed.