• 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 ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Connection Pool Problem in weblogic 9.2 MP3

 
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Current Cofiguration:
We are using Weblogic 9.2 MP3 and Oracle 10g.
We have One Admin Server and two managed Node .. But these are not in any Cluster.
The underlaying database is HA configured .There are 6 datasource for each 6 VIP in Weblogic for Database connection.
And these 6 datasource are bind with single multiple datasource with failover algorithm enabled.
Also these 6 datasource have the below property .....
Database Driver:Oracle's Driver(Thin) Version:9.0.1,9.2.0,10
Test Connections On Reserve :TRUE
Shrink Frequency :900
Ignore In-Use Connections: TRUE
Remove Infected Connections Enabled:TRUE
Initial Capacity: 1
Maximum Capacity: 100
Capacity Increment: 1

Property for mutidatasource
Failover Request if Busy :FALSE
Failover Callback Handler: NONE


Problem Descriptio:
After someday interval we are getting the below error in our log

[java.sql.SQLException: weblogic.common.ResourceException:
MultiDataSource(DataSource009): weblogic.common.resourcepool.ResourceLimitException:
No resources currently available in pool DataSource009 to allocate to applications, please increase the size of the pool and retry..

And no failover is happening .also in bea log it is just saying DataSource009 as closed. No other message is there.
While monitoring this datasource

Server managed1_wls01
Active Connections Current Count :0
Active Connections :4
Connection Delay Time: 1657
Current Capacity :4
Current Capacity Hight Count:3

Server managed2_wls01
Active Connections Current Count:1
Active Connections :8
Connection Delay Time:998
Current Capacity :2
Current Capacity Hight Count:7

we can see this data dource in no node is touching the Maximum Capacity as : 100
So why the above error is comming and what is the resolution ?
 
Bartender
Posts: 6663
5
MyEclipse IDE Firefox Browser Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Does you DB allow 100 connections to be served ?

A stress test in the DEV environment should sort this out easily
 
Anish Kuti
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Good point .. I will check allowed number of database connection.
But do not know which parameter to check.
We have done stress test in dev .. but no clue what is heppening in prod .
 
Deepak Bala
Bartender
Posts: 6663
5
MyEclipse IDE Firefox Browser Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ask a DBA about how many connections can be served.

If it makes sense, do a stress test on prod on a week end or a time when there is no traffic. If it is an internal application and management will tolerate a crash + restart to identify the problem, then this can be an option
 
Anish Kuti
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Deepak,

Just chcek with DBA .. and found that conenction limit is set as "UNLIMITED" in profile for the database user.

Regarding the stress test for user in Live .. we have already done that fo view api call ..But no problem found in connection pool . Are you seeing any issue in connection pool configuration ?
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic