Database connections from Rational Team Concert
How does IBM Rational Team Concert (RTC) initiate connections to the database?
It is important to understand how connections are being made from the application to the database when implementing database tuning.
Activities like opening a work item will create a connection to the DB, but ultimately, it is the services within the server that will initiate the database connections.
A task that the user does might use a number of services, which in turn might use a number of transactions, thus making a connection for each transaction. Connections are not made to the database when a user logs in, but rather when a service requests a connection.
The database connections will wait a maximum of 3000 ms before becoming idle. In RTC versions pre 4.0, the idle connections are not dropped. New connections are added until the JDBC Connection pool is full, and at that point, the idle connections are reused by new services. The JDBC Connection Pool Size is by default 128 as per RTC Advanced properties.
To learn more about Tuning the RTC Server JDBC Connection settings, review the following articles:
Jazz and Rational Team Concert have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki.
Translate this page: