wood burning stoves 2.0*
The moose likes JDBC and the fly likes java.sql.SQLException: No available resource. Wait-time expired. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Databases » JDBC
Bookmark "java.sql.SQLException: No available resource. Wait-time expired." Watch "java.sql.SQLException: No available resource. Wait-time expired." New topic
Author

java.sql.SQLException: No available resource. Wait-time expired.

RajKumar Boga
Greenhorn

Joined: Apr 26, 2006
Posts: 9
Hi All,

I am using Sun Application Server 7 and backend is Oracle 9i.
In our project we are getting Exception as follows:


(i.e there are may be connections/cursors not closing at Database side
even if i am closing the connection as follows :



Is there any other way to close the connction?

thanks and regards
Rajkumar Boga
vishwanath nadimpally
Ranch Hand

Joined: Jan 25, 2005
Posts: 116


This is the preferred way of closing the db resources.
RajKumar Boga
Greenhorn

Joined: Apr 26, 2006
Posts: 9
Hello,


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!

Regards
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: java.sql.SQLException: No available resource. Wait-time expired.