When we start Process Automation it stops and records following error in the c2o.log file. ERROR [org.hibernate.util.JDBCExceptionReporter] [ckThreadTimer-8] Unable to get managed connection for RuntimeLibDS;

We are unable to start and use Process Automation as the service stops immediately after start recording following errors in the c2o.log file.

 ERROR [org.hibernate.util.JDBCExceptionReporter] [ckThreadTimer-8] Unable to get managed connection for RuntimeLibDS; - nested throwable: (javax.resource.ResourceException: Unable to get managed connection for RuntimeLibDS)

ERROR [com.optinuity.c2o.events.GetClusterwideLockThread] [ckThreadTimer-8] EventManager[checkIfGlobalLockTableFree] error: Cannot open connection

ERROR [org.hibernate.util.JDBCExceptionReporter] [        Timer-9] Unable to get managed connection for OptinuityDS; - nested throwable: (javax.resource.ResourceException: Unable to get managed connection for OptinuityDS)

ERROR [com.optinuity.c2o.agenda.C2OAgendaInterpreter] [        Timer-9] Failed to build list of tasks for the day; will retry if master

This error is seen when connections to database exceed the threshold which is by default set to 100.

- Connect to Process Automation server

- Take a backup of 'oasis-ds.xml' file located in '.PAM\Server\C2O\ext-deploy' direcotory 

   For ex: 'E:\Program Files\CA\PAM\server\c2o\ext-deploy'

- Edit the file and change the max-pool size value from 100 to 300 in the following sections

<datasources>

  <local-tx-datasource>

    <jndi-name>OptinuityDS</jndi-name>

    <connection-url>${oasis.database.connectionurl}${oasis.database.lib.dbname:itpamlib}${oasis.database.additionalparamurl}</connection-url>

    <driver-class>${oasis.database.driver}</driver-class>

    <user-name>${oasis.database.username}</user-name>

    <password>${oasis.database.password}</password>

    <max-pool-size>300</max-pool-size>

local-tx-datasource>

    <jndi-name>RuntimeLibDS</jndi-name>

    <connection-url>${oasis.runtime.database.connectionurl}${oasis.runtime.database.dbname:runtimeLib}${oasis.runtime.database.additionalparamurl}

    </connection-url>

    <driver-class>${oasis.runtime.database.driver}</driver-class>

    <user-name>${oasis.runtime.database.username}</user-name>

    <password>${oasis.runtime.database.password}</password>

    <max-pool-size>300</max-pool-size>

Note: These errors will also seen while PAM server is up and running, in such cases same steps can be performed without restarting the service.