In PRPC 7.1.4, you selected Use JDBC Connection Pool for the field on the Database tab of a Database form to use a connection pool defined by a Java Naming and Directory Interface (JNDI) facility.
However, when you start the System Management Application (SMA), select> , select a database name, then click the button to monitor the database connection details, there are no connections listed under .
Changes were implemented starting in PRPC 7.1 to support split schema and how database connections are managed. The changes include deprecating some old and unused settings, and having application servers manage database connections, rather than PRPC.
In PRPC 7.1.x, in most cases, SMA’s Managed Connections table only shows connections that are actively being used. Prior to 7.1, if you selected Use JDBC Connection Pool for the field on the Database tab of a Database form, SMA showed a pool of database connection wrapper objects, some of which were not tied to active database connections.
Starting in PRPC 7.1, SMA only shows database connections under conditions such as the following.
- If you select Use JDBC Connection Pool for the field on the Database tab of the Database form, SMA’s Managed Connections table only shows connections that are actively being used.
- If you select Use configuration in preferences for the field on the Database tab of a Database form, connections are not passivated. As a result, SMA’s Managed Connections table still shows these connections, even if they are no longer being used.
SMA Changes Introduced in PRPC 7.1.5
Starting in PRPC 7.1.5, when you start SMA and select> , the label for the second column of the table has been updated from to to make it clear that those are the only connections you can expect to see in this table.
In addition, once you select a database name and click thebutton, you’ll notice that the label for the table that shows you the database connection details has been updated from to .