• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
  • Mike London

weblogic.jdbc.extensions.PoolLimitSQLException: No resources currently available in pool

Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

I am using Oracle driver for connection in datasource in Weblogic 10.3 in my application. I am getting the below exception after I do the search activity number of times ,which uses the connection in this datasource to run a Stored procedure.

weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool

I have checked my code thouroughly and there is no connection leak. The connection is closed properly in all possible scneario's. I have verified the same by running the application and then checking the log file immediately.
The initialcapacity and maxcapacity of the datasource is 1 and 15 respectively. After I get the above exception, if I check the weblogic console, I find in the left bottom corner a window "System status", which has links like "Failed", "Critical", "Overloaded", "Warning" and "Ok". When I clicked on the "Overloaded" link it shown below,

"JDBC Overloaded Connection Pool Name = null:null:OracleCSIDataSource, State = Overloaded "!

Thanks & Regards
Ranch Hand
Posts: 32
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ashwin,

when the application is making too much call to DB and the DB connections are not released then comes the OVERLOADED issue.

But WL 9 and above versions of the servers having some control functions to connection pools

So you can stop the connection pool, refresh it and restart it again

to do this

go to

Services->Data Sources-><select the particular Data source> -> Control

this will shows the conditions of the Data source in all servers it has been targeted. Now check the respective server with overloaded issue and do STOP - CLEAR THE CONNECTION CACHE -- START

this is only a workaround. for complete resolution you have to monitor the DB usage and according to that you have to tune the connection pool parameters.

Consider Paul's rocket mass heater.
    Bookmark Topic Watch Topic
  • New Topic