Bug 1135482

Summary: ClassNotFoundException with webservice resource-adapter
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Jan Stastny <jstastny>
Component: IntegrationAssignee: Van Halbert <vhalbert>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: dlesage, felias, mmakovy, vhalbert
Target Milestone: ER5Keywords: QA-Closed, Reopened
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When the user queried a VDB whose source is a web service, an exception would occur. An update to the connector-ws has resovled this issue. As a result, users querying web service-courced VDBs will no longer encounter this exception.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 08:48:19 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:
Embargoed:
Attachments:
Description Flags
tar with vdb, resource-adapter and queries definitions none

Description Jan Stastny 2014-08-29 12:36:41 UTC
Created attachment 932663 [details]
tar with vdb, resource-adapter and queries definitions

Description of problem:
When querying vdb whose source is a webservice, then following exception occurs:

ERROR [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue77) Connector worker process failed for atomic-request=bl5M9qEZIVcU.13.1.20: java.lang.NoClassDefFoundError: javax/ws/rs/client/ClientException
.
.
.
Caused by: java.lang.ClassNotFoundException: javax.ws.rs.client.ClientException from [Module "org.apache.cxf.impl.frontend-jaxrs:main" from local module loader @11c836e8 (finder: local module finder @6f8cc276 (roots: /home/jstastny/DV-6.1.0/jboss-eap-6.3/modules,/home/jstastny/DV-6.1.0/jboss-eap-6.3/modules/system/layers/dv,/home/jstastny/DV-6.1.0/jboss-eap-6.3/modules/system/layers/base))]
.
.
.

Version-Release number of selected component (if applicable):
DV 6.1.0-ER1 (also DV 6.1.0-DR2)

How reproducible:
Each time the vdb is queried.

Steps to Reproduce:
1. add resource-adapter to standalone.xml
2. deploy vdb
3. start server
4. either connect with teiid-driver from a sql querying tool, or with SQLBulkQueryTool and execute one of given queries
5. run a query

Actual results:
ClassNotFoundException

Expected results:
Result set

Additional info:

Comment 2 Van Halbert 2014-08-29 12:51:46 UTC

*** This bug has been marked as a duplicate of bug 1130665 ***

Comment 3 Jan Stastny 2014-10-23 10:03:07 UTC
This problem still occurs.

This bug was marked as duplicate of a bug within dom4j module. The "dom4j bug" should have been resolved with ER2. I don't know how to check that one, but my issue (which is marked as duplicate) still remains.

I assume that referenced "bug 1130665" was successfully resolved in ER2 as there is no activity on that one, therefore I reopen this bug as it seems that it should not have been considered as duplicate of mentioned bug.

Comment 4 Van Halbert 2014-10-28 18:37:07 UTC
<jdc> vhalbert: I think that it would be cleanest to provide our own javax/ws/rs/api/main module, replacing jboss-jaxrs-api_1.1_spec-1.0.1.Final-redhat-2.jar with javax.ws.rs-api.2.0.1.jar.

Comment 5 Van Halbert 2014-10-28 18:50:27 UTC
*** Bug 1146952 has been marked as a duplicate of this bug. ***

Comment 6 Van Halbert 2014-10-29 14:54:40 UTC
It has been validated by TEIIDDES-2284 that applying the updated jar fixes the issue.

Comment 7 JBoss JIRA Server 2014-10-29 19:56:26 UTC
Ted Jones <tejones> updated the status of jira TEIIDDES-2284 to Resolved

Comment 8 Van Halbert 2014-11-24 20:12:10 UTC
Teiid has committed the fix upstream to add the use of the 2.0 version as slot=2.0.  No need for productization to add an override to the build.

Comment 9 Van Halbert 2014-11-25 19:44:17 UTC
TEIID kit will be updated to have the spring framework 3.2.12 version (https://bugzilla.redhat.com/show_bug.cgi?id=1166378) and the ClassNotFoundException will be fixed by changing to use name="javax.ws.rs.api" slot="2.0".   This is all associated with updating the connector-ws.

Comment 10 JBoss JIRA Server 2015-03-09 11:47:08 UTC
Matus Makovy <mmakovy> updated the status of jira TEIIDDES-2284 to Closed