OID 11g DIP SchedulerDS Could Not Create Pool Connection (Doc ID 1336964.1)

Last updated on JUNE 30, 2017

Applies to:

Oracle Internet Directory - Version 11.1.1 to 11.1.1 [Release 11g]
Information in this document applies to any platform.
DIP, DIP Quartz Scheduler, DIP MBeans


Symptoms

11g DIP from time to time stops working. Quartz Scheduler and MBeans are down in FMW control.

In logs the following errors appear:

#------wls_ods1_diagnostic.log------
[2011-05-18T10:50:56.392+01:00] [wls_ods1] [ERROR] [] [org.quartz.impl.jdbcjobstore.JobStoreTX] [tid: QuartzScheduler_DefaultQuartzScheduler-oid1v.company.com1305710418254_ClusterManager] [userId: <anonymous>] [ecid: 0000J02WyM95mZG6yzedMG1DoswF00000I,0] [APP: DIP#11.1.1.2.0] ClusterManager: Error managing cluster: Failed to obtain DB connection from data source 'schedulerDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Socket read timed out[[
org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'schedulerDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Socket read timed out [See nested exception: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Socket read timed out]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:636)

.....
[2011-05-18T11:30:57.034+01:00] [wls_ods1] [ERROR] [] [org.quartz.impl.jdbcjobstore.JobStoreTX] [tid: QuartzScheduler_DefaultQuartzScheduler-oid1v.company.com1305710418254_ClusterManager] [userId: <anonymous>] [ecid: 0000J02WyM95mZG6yzedMG1DoswF00000I,0] [APP: DIP#11.1.1.2.0] ClusterManager: Error managing cluster: Failed to obtain DB connection from data source 'schedulerDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool schedulerDS is Suspended, cannot allocate resources to applications..[[
org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'schedulerDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool schedulerDS is Suspended, cannot allocate resources to applications.. [See nested exception: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/schedulerDS' weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool schedulerDS is Suspended, cannot allocate resources to applications..]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:636)
at org.quartz.impl.jdbcjobstore.JobStoreTX.getNonManagedTXConnection(JobStoreTX.java:72)


#------listener.log----------------
18-MAY-2011 10:49:53 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=oid1v)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647040)) * status * 0
18-MAY-2011 10:49:53 * service_died * LsnrAgt * 12537
18-MAY-2011 10:49:53 * version * 0
Dynamic address is already listened on (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oid1v.company.com)(PORT=1521)))
18-MAY-2011 10:49:53 * service_register * LsnrAgt * 0
Wed May 18 10:50:03 2011
18-MAY-2011 10:50:03 * service_update * oidl1 * 0
18-MAY-2011 10:50:04 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=oidl1.company.com)(CID=(PROGRAM=emagent)(HOST=oid1v)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.109)(PORT=25812)) * establish * oidl1.company.com * 0
Wed May 18 10:50:36 2011
18-MAY-2011 10:50:36 * service_update * oidl1 * 0
Wed May 18 10:50:54 2011
WARNING: Subscription for node down event still pending
.....

18-MAY-2011 11:29:48 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=oidl1.company.com)(CID=(PROGRAM=emagent)(HOST=oid1v)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.109)(PORT=36172)) * establish * oidl1.company.com * 0
Wed May 18 11:30:00 2011
WARNING: Subscription for node down event still pending
18-MAY-2011 11:30:00 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=oid1v)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647040)) * status * 0
18-MAY-2011 11:30:00 * service_died * LsnrAgt * 12537
18-MAY-2011 11:30:01 * version * 0
Dynamic address is already listened on (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oid1v.company.com)(PORT=1521)))
18-MAY-2011 11:30:01 * service_register * LsnrAgt * 0
18-MAY-2011 11:30:04 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=oidl1.company.com)(CID=(PROGRAM=emagent)(HOST=oid1v)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.109)(PORT=36232)) * establish * oidl1.company.com * 0
Wed May 18 11:31:00 2011
WARNING: Subscription for node down event still pending
18-MAY-2011 11:31:00 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=oid1v)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647040)) * status * 0
18-MAY-2011 11:31:00 * service_died * LsnrAgt * 12537

Changes

No relevant changes on server. If 11g stack is restarted, DIP is back to running status, Quartz Scheduler and MBeans are up, synchronization is working fine. Nevertheless after some random time, the issue appears again.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms