Catalog max connection pool size: 100

Question

Seeing this message repeated every 10 seconds in the RSHostingService_yyyy_mm_dd_hh_mm_ss.log file.

Can anyone advise:

a) Why this is being reported so frequently?

b) Does it indicate the limit is being hit?

c) If b is true, how can I increase it?

Thanks.

Answer 1

The message indicating that the catalog max connection pool size is set to 100 suggests that the application is reaching the limit of available connections in the pool. Here are the answers to your questions:

a) Why this is being reported so frequently?
This message is likely reported frequently because the application is attempting to create new connections but is unable to do so due to the maximum connection pool size being reached. This can happen if there are many concurrent requests or if connections are not being released back to the pool in a timely manner.

b) Does it indicate the limit is being hit?
Yes, if you are seeing this message repeatedly, it indicates that the limit of 100 connections is being hit, and the application is unable to establish new connections until some are released back to the pool.

c) If b is true, how can I increase it?
To increase the maximum pool size, you would typically need to modify the connection string or configuration settings for your SQL Server Reporting Services. Look for a property related to the connection pool size in your configuration files or connection strings and increase the value accordingly. For specific instructions, refer to the documentation for SQL Server Reporting Services or your database connection settings.

---

References:

• Distributed Relational Database Architecture (DRDA) Protocol Errors
• Data Provider Error Codes