You're absolutelly right Marc,
but the connection is being described by the connection context
containing the username and the password. Each application has its own
DB account, so as you have written bellow, the application gives the
connection back to the pool BUT only the same application
This sounds like poor coding to me. Your application should get the
connection object from the pool and immediately release when done. Having
an application hold onto a connection (especially in client/server) world is
bound to cause you to run out of connections or reach timeouts.
On 5/2/06, M
Hi all,
I have a problem with connection pooling.
Example:
- about 30 applications using the pool
- each application uses 1 DB username/password (30 users)
imagine following situation:
Only 1 application works hard, the others do nothing. This application
takes for example 80% of all possible co
