Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1514019

Summary: JDG source model with 'v' letter at beginning of a name doesn't work.
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Matej Kralik <mkralik>
Component: TeiidAssignee: David Le Sage <dlesage>
Status: CLOSED WONTFIX QA Contact: Matej Kralik <mkralik>
Severity: medium Docs Contact:
Priority: high    
Version: 6.4.0CC: blafond, drieden, gjospin, jolee, jschatte, thauser, vhalbert
Target Milestone: GAKeywords: Documentation
Target Release: 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
When the name of a Red Hat JBoss Data Grid source model starts with the letter 'v', after you run a query on a materialized table you will encounter an exception. To work around this issue, avoid starting your source models with 'v' if you are using Red Hat JDG.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-01 03:33:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matej Kralik 2017-11-16 13:51:16 UTC
Description of problem:
When the name of a JDG source model starts with 'v' letter, after run query at the materialized table (BooksMatView.viewBooks in attached VDB), the server shows exception:

ERROR [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue176) Connector worker process failed for atomic-request=X6jNnAMTIgyp.0.6.248: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=551 returned server error (status=0x85): java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks

For more information see linked JIRA.

Comment 2 David Le Sage 2017-11-21 04:29:19 UTC
Added to Release Notes errata as a known issue.

Comment 4 David Le Sage 2018-02-01 03:33:56 UTC
Documentation known issue verified but engineering unresolved.