ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Database connectivity failed with The internal connection pool has reached its maximum size and no connection is currently available error

book

Article ID: 226283

calendar_today

Updated On:

Products

CA Service Operations Insight (SOI)

Issue/Introduction

SOI 4.2 

 

SOI MANAGER @ http://hostname:7090 (HTTP/1.1).

DB access layer has initialized correctly.

Detected REMOTE DB connection to:

    jdbc:sqlserver://hostname;databaseName=SAMStore

 

ACCESS tests...

 

- Preloaded table test (CIFamily):

    Completed [0ms] - fetched 9 records.

    Expecting immediate response (< 5ms).

    GOOD

 

- Internal table load test (CIFamily):

               Test failed.

               EX:org.hibernate.HibernateException: The internal connection pool has reached its maximum size and no connection is currently available!

 

Performance tests cannot be performed.

 

Report prep time: 2ms

(end-of-report)

 

Environment

Release : 4.2

Component : Service Operations Insight (SOI) Manager

Resolution

To prevent problem from occurring do the following

Edit \soi\tomcat\lib\hibernate.cfg.xml

Change value to 200 for line

<property name="connection.pool_size">30</property>

 

Restart the SOI Application Server service is require to take effect.