This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
i am having maximum 100 connections(initial 50, increment=5,max=100) configured in my connection pool. in the application runtime 100 users are already using the connections. now the App. Server is not allowed to create another.
now my ques. is.. 101th user has come in, and he wants to do an urgent updation in the DB and he needs a connection.He cant wait b'coz he is in a time bound application.in time he has to update his work, or else it is waste.
now how can the 101th user can get the connection? what the application server is going to do in this scenario?
The server doesn't know or care about request priority. It works on a first come, first served policy. It can't interrupt any current connections because that would break whatever the other users are doing and would leave the database in an unknown state. So it must wait for a connection and if this urgent request is the next in line, it will give it to him.
If you want to provide a priority-based connection system you will have to manage separate connection pools, reserving 1 or more connections for those high priority cases.
A well-written application will hold connections for the shortest duration possible, so no one should have to wait very long for a connection. How long does your application hold onto connections?
0
