Adapter for Apache Kafka 9.6 | webMethods Adapter for Apache Kafka Documentation | webMethods Adapter for Apache Kafka Installation and User’s Documentation | Package Management | Adapter for Apache Kafka in a Clustered Environment | Clustering Considerations and Requirements | Considerations When Configuring Connections with Connection Pooling Enabled
 
Considerations When Configuring Connections with Connection Pooling Enabled
When you configure a connection that uses connection pools in a clustered environment, be sure that you do not exceed the total number of connections that can be opened simultaneously for that database.
For example, if you have a cluster of two Integration Servers with a connection configured to a database that supports a maximum of 100 connections opened simultaneously, the total number of connections possible at one time must not exceed 100. This means that you cannot configure a connection with an initial pool size of 100 and replicate the connection to both servers, because there could be possibly a total of 200 connections opened simultaneously to this database.
In another example, consider a connection configured with an initial pool size of 10 and a maximum pool size of 100. If you replicate this connection across a cluster with two Integration Servers, it is possible for the connection pool size on both servers to exceed the maximum number of database connections that can be open at one time.
For information about configuring connections forAdapter for Apache Kafka, see Overview of Adapter for Apache Kafka Connections.
For more general information about connection pools, see the webMethods Integration Server Administrator’s Guide for your release.
Note:
To avoid receiving duplicate messages, Consumer Connection in the cluster must be configured with same groupId.