Maximum number of connections reached on IBM WebSphere InterChange Server

The following log is encountered while collaboration tries to implement database operation:

[MsgID: 11056] [Mesg: The server will be shut down because the collaboration cannot delete event XXX.Request from persistent storage. Business object keys = MQConfig=ID:XXX.Reason:An available connection in the cache cannot be found. Reach the maximum number of connections or can not scavenge connections anymore:

Current Pool Index: 0 Name: EVENT_MANAGEMENT Max Connections: 2147483647 Opend connections: 48 Avail Connections: 0 Scavenged Connections: 0

Current Pool Index: 1 Name: TRANSACTIONS Max Connections: 2147483647 Opend connections: 2 Avail Connections: 0 Scavenged Connections: 1

Current Pool Index: 2 Name: REPOSITORY Max Connections: 2147483647 Opend connections: 0 Avail Connections: 0 Scavenged Connections: 0

Current Pool Index: 3 Name: FLOW_MONITORING Max Connections: 2147483647 Opend connections: 0 Avail Connections: 0 Scavenged Connections: 0

Current Pool Index: 4 Name: USER_REGISTRY Max Connections: 2147483647 Opend connections: 0 Avail Connections: 0 Scavenged Connections: 0

]

Maximum number of connections is set to the default value 50. When the current number of database connections in connection pools equal to 50, above error will be encountered if the collaboration is trying to request a connection to perform database operation.

Increase the Max number of database connection allowed in the pool. You can choose any of the following ways to revisit the setting.

1. Edit the server configuration in System Manager, on "Database" tab, in "Database Connectivity" section increase the Maximum connections value.

2. On WICS box, launch IBM WebSphere InterChange Server Configuration Wizard, navigate to "Database" tab, in "Database Connectivity" section increase the Max Connections value.