Connection Management


This section explains the following connection management concepts:

Connection Pooling

Connection pooling is an efficient way of sharing of connections between different resources through creation, recycling and release of connections.

The adapter uses connection pooling to enhance the performance while communicating with a target application. Opening and maintaining a connection for each user or each request made to a target application is expensive in terms of both time and memory consumed while opening every new connection.

This is where the connection pool comes in. The adapter maintains a pool of already-established connections to the target application; so a thread can simply request a connection from the pool when it needs to, use it, and then release it back to the pool.

After a connection is created, it is placed in the pool and it is re-used so that a new connection does not have to be established for each new task. If all the connections are being used, a new request for a connection will have to wait until a connection in the pool becomes available. Connection pooling also cuts down on the amount of time a thread must wait because it doesn’t have to incur the delay inherent in establishing a connection to the target application.

Reconnection Mechanism

Sometimes, the adapter might lose the connection with a target application due to various reasons such as network problems or target application connectivity issues.

In such a scenario, the adapter uses the reconnection mechanism to dynamically restore the connection to the target application. The connection pool keeps track of the number of connections it established to the target application during its operation. After the network problems or target application connectivity issues are resolved, the adapter attempts to re-open the same number of connections to the target application prior to connection loss.

Each adapter provides reconnection configuration options that can be set using the TIBCO Designer.

An adapter service is suspended when the connection to the vendor application is broken. Upon reconnect, the adapter service resumes. No manual intervention is required. Here is how each type of service handles the reconnection scenario:

Connection Monitoring

The connection state can be monitored using TIBCO Hawk. An adapter sends an unsolicited notification to Hawk whenever adapter services are suspended. These unsolicited notifications are visible from all custom microagents defined for the adapter.

If the adapter:


TIBCO Adapter™ Concepts
April 2005
Copyright © TIBCO Software Inc. All rights reserved
www.tibco.com