Feedback
Did this article resolve your question/issue?

   

Article

Do we support both branded and unbranded pool.jar files in one mixed version JDBC drivers env?

Information

 
TitleDo we support both branded and unbranded pool.jar files in one mixed version JDBC drivers env?
URL Namedo-we-support-both-branded-and-unbranded-pool-jar-files-in-one-mixed-version-jdbc-drivers-env
Article Number000128221
EnvironmentProduct: Progress DataDirect for JDBC
Version : 5.1, 6.0
OS: JAVA
Database : DB2, Oracle, SQL Server
Application: All supported applications
Question/Problem Description
Current  branded environment consist of 3 different JDBC drivers 5.1.4 (DB2, Oracle, SQL Server) which contains one branded pool.jar file for connection pooling.
Planning to upgrade to the latest version  of the drivers which will make it as a mixed versions environment ( DB2 5.1.4, Oracle 6.0, SQL Server 6.0).
As per the distribution guide v5.1.4 and v6.0, it says branded pool.jar file for v5.1.4 needs to be distributed and unbranded pool.jar for v6.0 needs to be distributed.
So the result of this will create two pool.jar files (one branded, one unbranded) in one mixed version JDBC drivers env.
Will this mixed version JDBC drivers environment be supported?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Keeping Unbranded 6.0 and branded 5.1  pool.jar files in single folder will not be any issue and will be supported in the mixed version driver environment.
Workaround
Notes
Last Modified Date10/21/2019 10:07 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.