Tuning the JDBC data source of a messaging engine

The messaging engine needs to have the correct configuration for JDBC data source to achieve messaging performance on a service integration bus. Consider whether configure the connection pool for the JDBC data source to achieve the requirements for messaging performance. The messaging engine uses the connection pool to obtain its connections to the database. With a heavy workload, a messaging engine might require a large number of concurrent connections to avoid delays waiting for connections to become available in the pool. For example, a very heavily loaded messaging engine might need 50 or more connections. Complete the following steps to configure the connection pool to meet the performance requirements:

 

1. Ensure that the configuration of the relational database management system (RDBMS) permits the number of connections that you require. Refer to the documentation for the RDBMS for more information.

2. Use the admin console to set the connection pool parameters for the data source. Navigate to Resources > JDBC > Data sources > data_source_name > [Additional Properties] Connection pool properties .

   1. Set Maximum connections to the number of connections you require, for example, at least 50. The default number of connections is 10.

      Tip: If the messaging engine times out when requesting a database connection, check the error log. If the error log contains error message CWSIS1522E, increase the number of connections and verify the configuration of the RDBMS permits that number of connections.

   2. Set Purge policy to EntirePool. This policy enables the connection pool to release all connections when the messaging engine stops.

      You must set this value if the messaging engine can failover in a cluster.

   

---

Last updated Nov 10, 2010 8:23:07 PM CST