This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
This is the preferred way of closing the db resources.
Joined: Apr 26, 2006
yes i agreee to that i have tried that too, but still no luck. What happens is when i create a new connection the server takes a existing opened connection from the Container connection pool, and the only way to get this resourse back to the container is to close the connection after use which we are doing by using the connection.close() method.
But, i think the connections are not getting replace back to the connection pool, cause the pool size that we have fixed is 30 and it exceeds this 30 connection when we check the connections opened from the database side....
I think we are missing something here, if any body can help me out with this issue that it would be very great!