[
https://issues.jboss.org/browse/TEIID-3946?page=com.atlassian.jira.plugin...
]
Marcelo Guimarães commented on TEIID-3946:
------------------------------------------
I'm trying to get the information. They don't have the logs and the logs I have
didn't show the full stacktrace.
It's being difficult because they've updated JDV and, since the error don't
occur anymore, they don't have records of it now. (Even ETL tools is difficult because
it's happening on a "third party customer" - they're using JDV to
provide Data as a Service so the ETL tools is from their customers.)
Sorry for the trouble here.
Version negotiation in JDBC connection
--------------------------------------
Key: TEIID-3946
URL:
https://issues.jboss.org/browse/TEIID-3946
Project: Teiid
Issue Type: Feature Request
Components: JDBC Driver
Affects Versions: 8.7.4
Environment: - JDV 6.2
Reporter: Hisanobu Okuda
Assignee: Steven Hawkins
Fix For: 9.0
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)