Changes Coming to JDBC for UniData and UniVerse
Historically, processes connecting through JDBC have been capable of using Connection Pooling (CP) but were not consuming a Connection Pool license. This was due to an oversight in the JDBC code. As of UniData V7.2.X and UniVerse V10.3.X, applications that are using Connection Pooling through JDBC will be consuming a CP License.
If you use JDBC connectivity and are using CP, you should make sure that you have sufficient CP entitlements to support your application in order to maintain service levels consistent with previous releases of UniData or UniVerse.
The CP license will be released when the application using it exits. If no license is available, the process fails with a status code 99, indicating that UniData or UniVerse failed to obtain a CP license for the process.