search cancel

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

book

Article ID: 90217

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

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

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Resolution

Symptoms

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


Connections exceeded limit of 50 jdbc:oracle:thin:@xxx.xx.xx.xxx:1521:appmgrdg:AM_PROD

.....


Cause

The maximum number of connections to the database is exceeded.


Resolution

Applications Manager uses a connection pooling for the JDBC connections to the database. Normally as connections are no longer used, they are removed from the pool.

You can increase the number of connections by adding the following line in the Options.properties file (default setting is 50). The example shown below increases the number to 75:

MaxPooledConnections=75

Afterwards stop and restart the RmiServer:
>stopso rmiserver>startso rmiserver
Additionally, you can have your DBA check and eventually change a setting on the oracle database:

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