Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1303496

Summary:	Version negotiation in JDBC connection
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Hisanobu Okuda <hokuda>
Component:	Teiid	Assignee:	jolee
Status:	CLOSED WONTFIX	QA Contact:	Filip Elias <felias>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	aszczucz, blafond, dlesage, drieden, jolee, mbaluch, mguimara, thauser, vhalbert
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-15 19:46:49 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Hisanobu Okuda 2016-02-01 04:21:21 UTC

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:

Comment 6 jolee 2017-05-15 19:46:49 UTC

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.