Resolution:
Description:
============
How TIBCO ActiveMatrix® Adapter for Database manages connections to a database.

Environment:
===========
Windows/Linux/AIX/Solaris/HP platform
Oracle/SQL Server/DB2 Database
ADB Adapter 5.X, 6.X version

Resolution:
==========
TIBCO ActiveMatrix® Adapter for Database will create connections to database base on the configuration.

All connections will not be shared between threads and different kinds of services.

For the publisher, three connections will be created: one for polling, one for updating delivery status from N to P or N to C, and one for updating status from P to C.

NOTE the last connection will always be created and only be used when the transport is RVCM. The connections are shared between publisher services and are not configurable.

For the subscriber, seperate connections will be created for different RV or JMS sessions. Subscriber services using same RV/JMS session will share the connection.
Refer to the documentation on how to configure seperate connections/threads for subscribers under:

Configuration and Deployment ->  Chapter 4 Adapter Service Options  : Subscription Service Tabs -> Subscriber Options Tab -> Use Separate Service Thread

For a RPC service, connections will be created for each worker thread. Each worker will have its own connection. The number of worker threads is configurable, in adapter instance option. Refer to the document:

Configuration and Deployment -> Chapter 3 Adapter Instance Options ->  Chapter 3 Adapter Instance Options : Adapter Services Tab -> All Request-Response Services -> Number of Request-Response Service Threads

When the alerter is enabled, a connection will be created to receive the alerter message. When fault tolerance is enabled, a connection will be created to compete the mutex lock.

How does TIBCO ActiveMatrix® Adapter for Database manage connections to a database?