Connection Pooling

ActiveMatrix BusinessWorks creates a pool of JDBC connections for every JDBC Connection shared resource that uses the JDBC connection type. The maximum size of this pool is specified by the Maximum Connections configuration field.

Activities that use this JDBC Connection resource are given a connection from the pool. Once the maximum number of connections is reached, activities requesting a connection cannot proceed. Once a connection is freed by an activity, the connection is returned to the pool.

Connections that are left open, get eventually time out and be closed. These connections can be reopened at a later time, until the maximum number of connections specified in this field is reached. If you want to configure a timeout value for these connections, you can set the Engine.DBConnection.idleTimeout property. For more information, see TIBCO ActiveMatrix BusinessWorks™ Process Design.

If an activity detects a connection in the pool is invalid (for example, the database is restarted), the activity that uses the JDBC connection resource attempts to reestablish the connection.

All activities that are part of the same transaction, use the same connection in the connection pool. The first activity in a transaction attempts to reestablish an invalid connection. If a connection becomes invalid during a transaction, the transaction is rolled back and must be retried, if necessary.