[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2329:
--------------------------------
Fix Version/s: 9.0.4
(was: 9.2)
(was: 9.0.3)
> 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)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2326) REST/SOAP importers - Re use of the connection profile after restart
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2326?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2326:
--------------------------------
Fix Version/s: 9.0.4
(was: 9.0.3)
> REST/SOAP importers - Re use of the connection profile after restart
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2326
> URL: https://issues.jboss.org/browse/TEIIDDES-2326
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.0.4
>
> Attachments: nomodel.png
>
>
> Often times, as user I start the import of WSDL based or REST (with new one, or old with file and URL selection) service and go through the wizard, something does not work right. So, I typically remove the models generated, and then try the import process again. However, next time when I select the same connection profile I created before, I very seldom get same results. If I restarted the Designer for any reason, the previously created connection profile for sure does not work.
> It seems to me that, designer stores a temp XML/JSON file from where it starts processing, during the restart that gets deleted and import process instead of sending another request for the results document it fails with arbitrary error. There is no way to recover form it. IMO, REST and SOAP needs to be treated differently from XML File type sources and issue the query to get response document, not store it anywhere.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2568) NPE during the source synchronization with server
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2568?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2568:
--------------------------------
Fix Version/s: 9.0.4
(was: 9.0.3)
> 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
> Assignee: Ted Jones
> 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)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-1765) StateInfo example does not succeed
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1765?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1765:
--------------------------------
Fix Version/s: 9.0.4
(was: 9.0.3)
> StateInfo example does not succeed
> ----------------------------------
>
> Key: TEIIDDES-1765
> URL: https://issues.jboss.org/browse/TEIIDDES-1765
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Ted Jones
> Fix For: 9.0.4
>
>
> Walked thru the StateInfo example, and when I went to execute
> 12:55:47,190 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-/127.0.0.1:8080-1) Interceptor for {http://www.teiid.org/stateService/}stateService#{http://www.teiid.org/stateService/}GetAllStateInfo has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo.
> at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:106)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:237)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:95)
> at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:225)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:145)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> 12:55:47,195 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue27) Connector worker process failed for atomic-request=VUNHCCMa+sUf.0.9.3: org.teiid.translator.TranslatorException: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo.
> at org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:139)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:254) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:446) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:159) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:156) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_13]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_13]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> Caused by: javax.xml.ws.soap.SOAPFaultException: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo.
> at org.apache.cxf.jaxws.DispatchImpl.mapException(DispatchImpl.java:287)
> at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:392)
> at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:243)
> at org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:135)
> ... 13 more
> Caused by: org.apache.cxf.binding.soap.SoapFault: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo.
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:75)
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:46)
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:35)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
> at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:114)
> at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69)
> at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:800)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1696)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1532)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1440)
> at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:659)
> at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:530)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:463)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:366)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:319)
> at org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:354)
> at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:385)
> ... 15 more
> 12:55:47,199 WARN [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue28) TEIID30020 Processing exception for request VUNHCCMa+sUf.0 'TEIID30504 stateService: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo.'. Originally TeiidProcessingException Soap11FaultInInterceptor.java:75. Enable more detailed logging to see the entire stacktrace.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-1809) WAR File (REST, SOAP) Creation usability enhancements
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1809?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1809:
--------------------------------
Fix Version/s: 9.0.4
(was: 9.0.2)
(was: 9.0.3)
> WAR File (REST, SOAP) Creation usability enhancements
> ------------------------------------------------------
>
> Key: TEIIDDES-1809
> URL: https://issues.jboss.org/browse/TEIIDDES-1809
> Project: Teiid Designer
> Issue Type: Enhancement
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.0.4
>
>
> I have seen so many time in the community, where users are confused in asking them to create JNDI file to VDB and deploy the VDB and WAR file. I have two suggestions in this regard to help improve the situation
> 1) Instead of (or in addition) asking to enter {REPLACE_WITH_VDB_JNDI_NAME}, offer to create data source to the VDB. If the server is attached, you have all details, or pop up create datasource dialog to create.
> 2) Instead of (or in addition) to saving the WAR file, offer to deploy directly to the server, that will save time and would seem seamless operation we can provide.
> 3) I often find myself struck in figuring out what is WSDL Endpoint or what are REST endpoints exposed by the WAR deployed, it there is any help we can show at the end of this dialog box (if they choose to deploy) that would save time in them figuring out (going to documentation etc).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months