GUI is unresponsive, logs show 'Connections exceeded limit of XX errors

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

GUI is unresponsive, logs show 'Connections exceeded limit of XX' errors.

In most cases the GUI is unresponsive and the RmiServer log files contain error messages like this:

Connections exceeded limit of XX jdbc:oracle:thin:@xxx.xx.xx.xxx:1521:HOST:AM_NAME

Environment

CA Automic Applications Manager 9.x

Cause

The maximum number of connections to the database is exceeded.

Resolution

Applications Manager (AM) uses a connection pooling for the JDBC connections to the database. Normally as connections are no longer used, they are removed from the pool. There are 2 components that need to be updated to increase the total connection pool limit. One is an AM setting and the other is an Oracle settings.

While the example shown below increases the number to 300, this is only the recommend minimum for a production environment. 

For Applications Manager, increase the number of connections by adding the following line in the Options.properties file. 

MaxPooledConnections=300

Note that the default is 50 and if a MaxPooledConnections line is not present in the file, this means that the default value is being used.

A stop and restart of Applications Manager processes is required to apply changes.

In Oracle, refer to your DBA to check and change a setting on the oracle database:

For Oracle 12c or below:

You can increase the number of processes allowed in Oracle by modifying the init.ora file usually located in $ORACLE_HOME/dbs directory. A sample code is shown below:

$ORACLE_HOME/dbs/init$ORACLE_SID.ora
# processes=50
# SMALL
processes=150
# MEDIUM
#processes=200
# LARGE

For Oracle 19c:

Modern Oracle versions use SPFILE and to update the number of processes, you would have to run the below example sql:

ALTER SYSTEM SET processes=300 SCOPE=SPFILE;
SHUTDOWN IMMEDIATE;
STARTUP;

Note that your Oracle settings may already have a much higher value value for processes. If a higher value is already set, there is no need to update the value. Please refer to your DBA team for more info.