Description of problem: Our customer is providing a service on top of JDV and some of the external clients are still using outdated teiid drivers and wants something they can make for JDV to block a connection if the JDBC Driver used in a client is outdated. This scenario occurs everytime the customer updates JDV. Since there are so much external clients, some of them don't update their JDBC Drivers and this leads to some errors in JDV. Version-Release number of selected component (if applicable): JDV 6.2.x How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This and TEIID-3946 and the associated case all lack the information to properly document what errors are being thrown. I suggest we let the normal workflow occur here and an article be created when raised as an issue in SFDC and actual errors can be determined.