UCM 11g Login Page Is Inaccessible Because The CSDS Data Source Fails With "Could not create pool connection. The DBMS driver exception was: IO Error: Socket read timed out" (Doc ID 1302365.1)

Last updated on JUNE 06, 2017

Applies to:

Oracle WebCenter Content - Version 11.1.1.3.0 to 11.1.1.8.0 [Release 11g]
Information in this document applies to any platform.

Symptoms


After starting the UCM managed server, the UCM Login page is inaccessible and returns "Error 404--Not Found"

The messages in the console show that the UCM Server failed to initialize:

<Mar 8, 2011 5:04:39 PM IST> <Error> <oracle.ucm.idccs> <UCM-CS-050021> <UCM Server failed to initialize inside its servlet environment.>
<Mar 8, 2011 5:04:39 PM IST> <Error> <oracle.ucm.idccs> <UCM-CS-000001> <general exception
intradoc.common.ServiceException: !csProviderUnableToInitialize,SystemDatabase
at intradoc.server.IdcSystemLoader.loadProviders(IdcSystemLoader.java:2379)
at intradoc.server.IdcSystemLoader.initProviders(IdcSystemLoader.java:2132)
at intradoc.server.IdcSystemLoader.finishInit(IdcSystemLoader.java:401)
at intradoc.server.IdcSystemLoader.init(IdcSystemLoader.java:336)
at intradoc.server.IdcServerManager.init(IdcServerManager.java:120)
at intradoc.idcwls.IdcServletRequestUtils.initializeServer(IdcServletRequestUtils.java:624)
at intradoc.idcwls.IdcServletRequestUtils.initializeServer(IdcServletRequestUtils.java:455)
at intradoc.idcwls.IdcIntegrateWrapper.initializeServer(IdcIntegrateWrapper.java:102)
...
Caused By: intradoc.data.DataException: !csDbUnableToInitalize,SystemDatabase!csProviderFailedToExtractAndUseDataSource,CSDS
at intradoc.jdbc.JdbcManager.init(JdbcManager.java:92)
at intradoc.jdbc.JdbcWorkspace.init(JdbcWorkspace.java:77)
at intradoc.provider.Provider.init(Provider.java:71)
...
Caused By: intradoc.data.DataException: !csProviderFailedToExtractAndUseDataSource,CSDS
at intradoc.provider.ProviderPoolManager.init(ProviderPoolManager.java:134)
at intradoc.jdbc.JdbcManager.init(JdbcManager.java:79)
at intradoc.jdbc.JdbcWorkspace.init(JdbcWorkspace.java:77)
at intradoc.provider.Provider.init(Provider.java:71)
...
Caused By: intradoc.common.ServiceException: !csProviderFailedToAccessDataSource
at intradoc.provider.ProviderPoolManager.computeExternalConnectionObject(ProviderPoolManager.java:263)
at intradoc.provider.ProviderPoolManager.init(ProviderPoolManager.java:130)
at intradoc.jdbc.JdbcManager.init(JdbcManager.java:79)
at intradoc.jdbc.JdbcWorkspace.init(JdbcWorkspace.java:77)
at intradoc.provider.Provider.init(Provider.java:71)
at intradoc.server.IdcSystemLoader.loadProviders(IdcSystemLoader.java:2369)
...
Caused By: intradoc.common.ServiceException: !csUnableToExecMethod,getConnection
at intradoc.common.ClassHelperUtils.convertToStandardException(ClassHelperUtils.java:202)
at intradoc.common.ClassHelperUtils.convertToStandardExceptionAndThrow(ClassHelperUtils.java:179)
...
Caused By: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Socket read timed out
at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:250)
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:352)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:369)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at intradoc.common.IdcMethodHolder.invokeMethod(IdcMethodHolder.java:86)
at intradoc.common.ClassHelperUtils.executeIdcMethodConvertToStandardExceptions(ClassHelperUtils.java:406)
at intradoc.provider.ProviderPoolManager.getExternalRawConnection(ProviderPoolManager.java:945)
at intradoc.provider.ProviderPoolManager.computeExternalConnectionObject(ProviderPoolManager.java:243)
at intradoc.provider.ProviderPoolManager.init(ProviderPoolManager.java:130)
at intradoc.jdbc.JdbcManager.init(JdbcManager.java:79)
at intradoc.jdbc.JdbcWorkspace.init(JdbcWorkspace.java:77)
...


It looks like the CSDS datasource was unable to construct a connection to the database due to this error:
"weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Socket read timed out"

To confirm that this is a timeout issue:

- Login to WLS Console (typically http://<server>:7001/console)
- Navigate to Services->Data Sources
- Click on the Monitoring tab.
- Click on the CSDS data source link for the server in question.
- Click on the radio button for the server that is causing the problem (typically UCM_server1).
- The Test Data Source button is enabled. Click it.

The result will appear just below the Messages title at the top of the page. If it takes 10-15 seconds for the error to appear then this is likely a timeout problem. 

 

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