Weblogic 10.3 not allocating initialcapacity..

Question

I have a problem wherein i am not getting the initial capacity set to what i want to be until i restart the datasource . Following is my wstl that i used for creating the datasource..
cmo.setUrl('${datasource.url}')
cmo.setDriverName('com.ibm.u2.jdbc.UniJDBCDriver')
cmo.setPassword('${mhc.password}')
cd('/JDBCSystemResources/DS1/JDBCResource/DS1/JDBCConnectionPoolParams/DS1')
cmo.setTestConnectionsOnReserve(true)
cmo.setInitSql('SQL call PQCS.PINGCHECK(\'1\')\r\n')
cmo.setTestTableName('SQL call PQCS.PINGCHECK(\'1\')\r\n')
cmo.setInitialCapacity(15)
cd('/JDBCSystemResources/DS1/JDBCResource/DS1/JDBCDriverParams/DS1/Properties/DS1')
print('Priting user resources')
userProps=ls()
if(userProps.find('user')!=-1):
print 'user property already exists Targetting it now'
cd('/SystemResources/DS1')
set('Targets',jarray.array([ObjectName('com.bea:Name=MyServer,Type=Server')], ObjectName))
activate()
disconnect()
exit()
cd('/JDBCSystemResources/DS1/JDBCResource/DS1/JDBCDriverParams/DS1/Properties/DS1')
cmo.createProperty('user')
cd('/JDBCSystemResources/DS1/JDBCResource/DS1/JDBCDriverParams/DS1/Properties/DS1/Properties/user')
cmo.setValue('${user}')
cd('/JDBCSystemResources/DS1/JDBCResource/DS1/JDBCDataSourceParams/DS1')
cmo.setGlobalTransactionsProtocol('OnePhaseCommit')
cd('/SystemResources/DS1')
set('Targets',jarray.array([ObjectName('com.bea:Name=MyServer,Type=Server')], ObjectName))
activate()
exit()
When I go and look in the console i see 15 in the initial capacity but when i start the wldf console extension i see that it shows only 1 to be the current capacity . After i restart the DataSource alone i see that it is giving me back 15 connections as i want to.
Why is this happening? This has subsequently given me weblogic pool exhausting exceptions .
weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.Res
ourceLimitException: No resources currently available in pool DS1 to allocate to
applications, please increase the size of the pool and retry..
Please help..

Answer 1

Yes. If weblogic makes you a pool of 15 connections, and then you kill the DBMS,
how many connections do you have? When the pool finds all these dead
connections, and removes them, and can't make any replacements, it, and
you have zero connections and there's nothing we can do about it.
When the DBMS comes back up, and the pool finds out about it by trying
to reconnect, it will make connections one at a time as needed. The next
WLS release will slowly grow the pool back to the initial capacity even without
application load. All previous WLSes will grow one connectiuon on it's own, but
leave the full repopulate to application load needing it.
Yes, the number available and current capacity numbers should be correct,
so if you get a PoolLimitException, we would want to debug who the pool
thinks has all the connections.
Joe