Increasing the Number of SQL Server Active Connections in RDM

RDM application uses connection pooling which is handled by the application server. Applications that use connection coalescence maintain open connections in a pool. When the application requires access to the database, it simply uses an existing connection from the pool and establishes a new connection only if no pooled connections are available. This reduces the overhead enactments associated with connecting to the database to serve individual requests.

Is there a possibility to increase the maximum number of active connections of the application server pool?

Connection pools can be configured with restrictions to the number of minimum connections, maximum connections, and idle connections to optimize the performance of pooling in specific problem contexts and environments. When wishing to set up maximum active connections and idle connections, go to [RDM]/tomcat/conf/Catalina/localhost/rdm.xml, where Tomcat configurable parameters are located. They are as follows:
maxActive - The maximum number of active connections that can be allocated from a pool at the same time.
maxIdle - The maximum number of connections that should be kept in a pool at all times.

The connections are not closed, though. This is because connection pool keeps the connection open for further usage. There may occur an error with exceeding number of open connections. The error occurs when the maximum number of simultaneous user connections allowed for an instance of SQL Server is lower than the maximum number of active connections that can be allocated from the pool concurrently. To overcome the issue, check the maximum number of simultaneous user connections allowed for an instance of SQL Server (select @@MAX_CONNECTIONS).