[JBoss JIRA] (TEIIDDES-2592) Connecting to remote server takes a very long time
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2592?page=com.atlassian.jira.plu... ]
Andrej Šmigala commented on TEIIDDES-2592:
------------------------------------------
[~blafond] you mean TEIIDDES-2582 ? According to the linked bz, that is an EAP issue (or possibly documentation issue).
> Connecting to remote server takes a very long time
> --------------------------------------------------
>
> Key: TEIIDDES-2592
> URL: https://issues.jboss.org/browse/TEIIDDES-2592
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 9.0.2, 9.0.3
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 9.2, 9.0.4
>
> Attachments: org.teiid.runtime.client.patch
>
>
> Any interaction with remote server, such as connecting, importing from teiid connection or listing vdbs and datasources takes a very long time (minutes) when there are many datasources (30+) defined on the server
> blafond: We're compiling lists of DS, Translator and VDB objects. DS's basically take 3 different CLI calls to pull together. If you're not carefull, this results in CLI calls, calling other CLI calls repeatedly
> blafond: 30 Data sources were resulting in 900 + calls to the server, when it should have been maybe.... 60
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2592) Connecting to remote server takes a very long time
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2592?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2592:
----------------------------------------
Note still an issue with finding/setting the Data Source driver name with these changes. Teiid Connection Importer fails because the driver name == NULL
> Connecting to remote server takes a very long time
> --------------------------------------------------
>
> Key: TEIIDDES-2592
> URL: https://issues.jboss.org/browse/TEIIDDES-2592
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 9.0.2, 9.0.3
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 9.2, 9.0.4
>
> Attachments: org.teiid.runtime.client.patch
>
>
> Any interaction with remote server, such as connecting, importing from teiid connection or listing vdbs and datasources takes a very long time (minutes) when there are many datasources (30+) defined on the server
> blafond: We're compiling lists of DS, Translator and VDB objects. DS's basically take 3 different CLI calls to pull together. If you're not carefull, this results in CLI calls, calling other CLI calls repeatedly
> blafond: 30 Data sources were resulting in 900 + calls to the server, when it should have been maybe.... 60
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2329:
----------------------------------------
No, data source needs to be defined. But in this case WS, FILE they could be static ones as there is no real connection information to physical sources you need to provide.
> WS translator Procedure definition defined in correctly
> -------------------------------------------------------
>
> Key: TEIIDDES-2329
> URL: https://issues.jboss.org/browse/TEIIDDES-2329
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.0.4
>
>
> TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
> {code}
> java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2329:
----------------------------------------
[~rareddy] Still not clear. Teiid Designer's use case is a user has a remote CSV or XML file they want to use as a source. Currently Designer helps the user construct the invokeHttp() procedure in a source model during import OR the user can generate those procedures in the New Model wizard first.
Is there a way to get the source procedure from the Teiid Server without a data source defined?
> WS translator Procedure definition defined in correctly
> -------------------------------------------------------
>
> Key: TEIIDDES-2329
> URL: https://issues.jboss.org/browse/TEIIDDES-2329
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.0.4
>
>
> TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
> {code}
> java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2329:
----------------------------------------
If you call using the named parameter syntax yes it can be called with and without. BTW, Designer should be always using that format. "getSchema" method on the Admin API will get you the metadata of the procedures.
> WS translator Procedure definition defined in correctly
> -------------------------------------------------------
>
> Key: TEIIDDES-2329
> URL: https://issues.jboss.org/browse/TEIIDDES-2329
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.0.4
>
>
> TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
> {code}
> java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2329:
----------------------------------------
[~rareddy] Will the Teiid runtime handle both the old invokeHttp() signature (procedure) and the new invokeHttp() with the additional contentType parameter? Do you have an interface/method in mind to expose those procedures?
> WS translator Procedure definition defined in correctly
> -------------------------------------------------------
>
> Key: TEIIDDES-2329
> URL: https://issues.jboss.org/browse/TEIIDDES-2329
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.0.4
>
>
> TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
> {code}
> java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2596) Create a document that combines Teiid server query methodology and SQL development with Teid Designer features
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2596:
--------------------------------------
Summary: Create a document that combines Teiid server query methodology and SQL development with Teid Designer features
Key: TEIIDDES-2596
URL: https://issues.jboss.org/browse/TEIIDDES-2596
Project: Teiid Designer
Issue Type: Feature Request
Reporter: Barry LaFond
The Teiid documentation provides a number of query optimization and tuning features and info. Teiid Designer provides a certain amount of SQL definition including union and join construction as well as building criteria and function expressions.
Would be nice to develop a guide/doc that combines our knowledgebase as an aid for users to model/test their SQL in Designer or for their View SQL in dynamic VDBs
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2329:
----------------------------------------
[~balfond] see more context in https://issues.jboss.org/browse/TEIID-3107
Also, we need to remove the static metadata definition of invokeHTTP and get it from the server, and same goes for File.
> WS translator Procedure definition defined in correctly
> -------------------------------------------------------
>
> Key: TEIIDDES-2329
> URL: https://issues.jboss.org/browse/TEIIDDES-2329
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.0.4
>
>
> TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
> {code}
> java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2568) NPE during the source synchronization with server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2568?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2568.
------------------------------------
Assignee: (was: Ted Jones)
Resolution: Rejected
This was fixed in 9.0.2 release (June 15, 2015).
> NPE during the source synchronization with server
> -------------------------------------------------
>
> Key: TEIIDDES-2568
> URL: https://issues.jboss.org/browse/TEIIDDES-2568
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.1
> Reporter: Ramesh Reddy
> Fix For: 9.0.4
>
>
> While working with REST importer, after importing the "source model" is not being synchronized with the server.
> I found this exception in the error log
> {code}
> java.lang.NullPointerException
> at org.teiid.designer.datatools.profiles.ws.WSConnectionInfoProvider.getTeiidRelatedProperties(WSConnectionInfoProvider.java:101)
> at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:127)
> at org.teiid.designer.runtime.preview.PreviewManager.ensureConnectionInfoIsValid(PreviewManager.java:527)
> at org.teiid.designer.runtime.preview.jobs.UpdatePreviewVdbJob.runImpl(UpdatePreviewVdbJob.java:124)
> at org.teiid.designer.runtime.preview.jobs.WorkspacePreviewVdbJob.runInWorkspace(WorkspacePreviewVdbJob.java:129)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2329:
----------------------------------------
[~rareddy] Assuming Teiid runtime would handle both the old invokeHttp() signature (procedure) and the new invokeHttp() with the additional contentType parameter?
> WS translator Procedure definition defined in correctly
> -------------------------------------------------------
>
> Key: TEIIDDES-2329
> URL: https://issues.jboss.org/browse/TEIIDDES-2329
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.0.4
>
>
> TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
> {code}
> java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months