[JBoss JIRA] (TEIIDDES-3130) Designer manually created REST War errors with large resultset
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3130?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-3130.
----------------------------------
Today, I tested rest procedure with my local database (30000 records). I was able to reproduce this issue in the old designer but not in the latest build, so it looks that issue is gone. I have closed it.
> Designer manually created REST War errors with large resultset
> --------------------------------------------------------------
>
> Key: TEIIDDES-3130
> URL: https://issues.jboss.org/browse/TEIIDDES-3130
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Tested in Teiid Designer 11.1, 11.0.1. JDV 6.3.8
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Labels: release_notes
> Fix For: 11.1.1
>
> Attachments: REST_POC.vdb, REST_POC_1.war, myrestpoc.zip
>
>
> Using "Generate REST War" on a VDB and deploying it with your VDB and testing with a large resultset, gives the below error :
> 09:26:18,587 SEVERE [org.teiid.rest] (http-127.0.0.1:8080-1) Exception in execute: {0}: java.lang.Throwable: java.sql.SQLException: java.lang.IllegalArgumentException: Null charset name
> at org.teiid.rest.services.TeiidRSProviderPost.execute(TeiidRSProviderPost.java:116) [classes:]
> at org.teiid.rest.services.REST_Views.MV_AUDIT(REST_Views.java:94) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_60]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_60]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_60]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_60]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:583) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:565) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:130) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.14.Final-redhat-2.jar:7.5.14.Final-redhat-2]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:151) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:656) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> Caused by: java.sql.SQLException: java.lang.IllegalArgumentException: Null charset name
> at org.teiid.rest.services.TeiidRSProviderPost.handleResult(TeiidRSProviderPost.java:167) [classes:]
> at org.teiid.rest.services.TeiidRSProviderPost.execute(TeiidRSProviderPost.java:112) [classes:]
> ... 29 more
> Caused by: java.lang.IllegalArgumentException: Null charset name
> at java.nio.charset.Charset.lookup(Charset.java:457) [rt.jar:1.8.0_60]
> at java.nio.charset.Charset.forName(Charset.java:528) [rt.jar:1.8.0_60]
> at org.teiid.query.function.source.XMLSystemFunctions.serialize(XMLSystemFunctions.java:1278) [org.teiid.runtime.client_11.1.0.v20170906-1613.jar:]
> at org.teiid.rest.services.TeiidRSProviderPost.handleResult(TeiidRSProviderPost.java:165) [classes:]
> ... 30 more
> 09:26:18,591 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (http-127.0.0.1:8080-1) RESTEASY000105: Failed to execute: javax.ws.rs.WebApplicationException
> at org.teiid.rest.services.TeiidRSProviderPost.createWebApplicationException(TeiidRSProviderPost.java:194) [classes:]
> at org.teiid.rest.services.TeiidRSProviderPost.execute(TeiidRSProviderPost.java:117) [classes:]
> at org.teiid.rest.services.REST_Views.MV_AUDIT(REST_Views.java:94) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_60]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_60]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_60]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_60]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:583) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:565) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:130) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.14.Final-redhat-2.jar:7.5.14.Final-redhat-2]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:151) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:656) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> If the "Auto-generate WAR" box is checked instead it works.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3130) Designer manually created REST War errors with large resultset
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3130?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-3130:
-----------------------------------
Labels: release_notes (was: )
> Designer manually created REST War errors with large resultset
> --------------------------------------------------------------
>
> Key: TEIIDDES-3130
> URL: https://issues.jboss.org/browse/TEIIDDES-3130
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Tested in Teiid Designer 11.1, 11.0.1. JDV 6.3.8
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Labels: release_notes
> Fix For: 11.1.1
>
> Attachments: REST_POC.vdb, REST_POC_1.war, myrestpoc.zip
>
>
> Using "Generate REST War" on a VDB and deploying it with your VDB and testing with a large resultset, gives the below error :
> 09:26:18,587 SEVERE [org.teiid.rest] (http-127.0.0.1:8080-1) Exception in execute: {0}: java.lang.Throwable: java.sql.SQLException: java.lang.IllegalArgumentException: Null charset name
> at org.teiid.rest.services.TeiidRSProviderPost.execute(TeiidRSProviderPost.java:116) [classes:]
> at org.teiid.rest.services.REST_Views.MV_AUDIT(REST_Views.java:94) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_60]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_60]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_60]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_60]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:583) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:565) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:130) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.14.Final-redhat-2.jar:7.5.14.Final-redhat-2]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:151) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:656) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> Caused by: java.sql.SQLException: java.lang.IllegalArgumentException: Null charset name
> at org.teiid.rest.services.TeiidRSProviderPost.handleResult(TeiidRSProviderPost.java:167) [classes:]
> at org.teiid.rest.services.TeiidRSProviderPost.execute(TeiidRSProviderPost.java:112) [classes:]
> ... 29 more
> Caused by: java.lang.IllegalArgumentException: Null charset name
> at java.nio.charset.Charset.lookup(Charset.java:457) [rt.jar:1.8.0_60]
> at java.nio.charset.Charset.forName(Charset.java:528) [rt.jar:1.8.0_60]
> at org.teiid.query.function.source.XMLSystemFunctions.serialize(XMLSystemFunctions.java:1278) [org.teiid.runtime.client_11.1.0.v20170906-1613.jar:]
> at org.teiid.rest.services.TeiidRSProviderPost.handleResult(TeiidRSProviderPost.java:165) [classes:]
> ... 30 more
> 09:26:18,591 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (http-127.0.0.1:8080-1) RESTEASY000105: Failed to execute: javax.ws.rs.WebApplicationException
> at org.teiid.rest.services.TeiidRSProviderPost.createWebApplicationException(TeiidRSProviderPost.java:194) [classes:]
> at org.teiid.rest.services.TeiidRSProviderPost.execute(TeiidRSProviderPost.java:117) [classes:]
> at org.teiid.rest.services.REST_Views.MV_AUDIT(REST_Views.java:94) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_60]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_60]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_60]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_60]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:583) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:565) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:130) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.14.Final-redhat-2.jar:7.5.14.Final-redhat-2]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:151) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:656) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> If the "Auto-generate WAR" box is checked instead it works.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3177) Add relational extension property "sequence" to support FunctionMethod object type in latest Teiid
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-3177:
--------------------------------------
Summary: Add relational extension property "sequence" to support FunctionMethod object type in latest Teiid
Key: TEIIDDES-3177
URL: https://issues.jboss.org/browse/TEIIDDES-3177
Project: Teiid Designer
Issue Type: Enhancement
Components: Extension Framework, Teiid Integration
Affects Versions: 11.1
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 11.1.2
Teiid 10.x translator logic added a new extension property called "sequence" for an object type of FunctionMethod.
Designer's relational model does not have that object type, so need to add the property to the relational.mxd and add the logic to expose the property of procedure's isFunction == TRUE and import/export that value via -vdb.xml and DDL features.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3175) MED for JDG7 set wrong NAMESPACE and properties prefix
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3175?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-3175.
------------------------------------
Fix Version/s: 11.1.2
Assignee: Barry LaFond
Resolution: Done
master: https://github.com/Teiid-Designer/teiid-designer/commit/515a7be11b8f468cf...
> MED for JDG7 set wrong NAMESPACE and properties prefix
> ------------------------------------------------------
>
> Key: TEIIDDES-3175
> URL: https://issues.jboss.org/browse/TEIIDDES-3175
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.1.2
>
>
> For workaround in this issue [TEIIDDES-3174|https://issues.jboss.org/browse/TEIIDDES-3174] I manually set MED (infinispan-hotrod) for JDG7 source model. When I create vdb as XML, xml file contains namespace _'http://www.teiid.org/translator/infinispan/2017' AS teiid_infinispan-hotrod_ but when I want to deploy it, on the server shows warning:
> {code:java}
> 13:07:54,108 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB BookMat.1 model "BookJDGSource" metadata failed to load. Reason:TEIID60017 Invalid prefix teiid_infinispan, teiid_ is reserved for Teiid use.: org.teiid.metadata.MetadataException: TEIID60017 Invalid prefix teiid_infinispan, teiid_ is reserved for Teiid use.
> {code}
> I also noticed that name of properties are *teiid_infinispan-hotrod* but should be *teiid_ispn*.
> Generated model in xml vdb:
> {code:java}
> SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2017' AS teiid_infinispan-hotrod
> CREATE FOREIGN TABLE viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_infinispan-hotrod:CACHE" 'books_indexed');
> CREATE FOREIGN TABLE ST_viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_infinispan-hotrod:CACHE" 'books_indexed_st');
> {code}
> Right model (in my opinion):
> {code:java}
> SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2017' AS teiid_ispn
> CREATE FOREIGN TABLE viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_ispn:CACHE" 'books_indexed');
> CREATE FOREIGN TABLE ST_viewBooks (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
> ) OPTIONS(UPDATABLE 'TRUE', "teiid_ispn:CACHE" 'books_indexed_st');
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-3174:
-----------------------------------
Workaround Description:
# Set up and run server if you don't have any server (infinispan-hotrod MED will be imported)
# Right click on generated JDG source model and select Modeling -> Manage Model Extension Definition
# Click to Add... and select infinispan-hotrod
# click to ok and finish button (now, model has set extension and property infinispan-hotrod:CACHE is set)
When you have genereated xml vdb, you must also rename prefix from *teiid_infinispan-hotrod* to *teiid_ispn* due to [TEIIDDES-3175|https://issues.jboss.org/browse/TEIIDDES-3175].
was:
# Set up and run server if you don't have any server (infinispan-hotrod MED will be imported)
# Right click on generated JDG source model and select Modeling -> Manage Model Extension Definition
# Click to Add... and select infinispan-hotrod
# click to ok and finish button (now, model has set extension and property infinispan-hotrod:CACHE is set)
> Infinispan-hotrod MXD is not set after JDG materialization wizard
> -----------------------------------------------------------------
>
> Key: TEIIDDES-3174
> URL: https://issues.jboss.org/browse/TEIIDDES-3174
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.1.2
>
>
> When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard.
> I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod).
> After that, I see infinispan-hotrod:CACHE which I defined in the wizard.
> Typ of infinispan-hotrod is *imported* so I must have set up a server *before*.
> In my point of view, the designer should set MED for JDG7 source model automatically.
> My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available.
> When I generate source model for JDG6.6, MED is set correctly (because MED is built-in).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3175) MED for JDG7 set wrong NAMESPACE and properties prefix
by Matej Kralik (JIRA)
Matej Kralik created TEIIDDES-3175:
--------------------------------------
Summary: MED for JDG7 set wrong NAMESPACE and properties prefix
Key: TEIIDDES-3175
URL: https://issues.jboss.org/browse/TEIIDDES-3175
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 11.1.1
Reporter: Matej Kralik
Priority: Critical
For workaround in this issue [TEIIDDES-3174|https://issues.jboss.org/browse/TEIIDDES-3174] I manually set MED (infinispan-hotrod) for JDG7 source model. When I create vdb as XML, xml file contains namespace _'http://www.teiid.org/translator/infinispan/2017' AS teiid_infinispan-hotrod_ but when I want to deploy it, on the server shows warning:
{code:java}
13:07:54,108 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB BookMat.1 model "BookJDGSource" metadata failed to load. Reason:TEIID60017 Invalid prefix teiid_infinispan, teiid_ is reserved for Teiid use.: org.teiid.metadata.MetadataException: TEIID60017 Invalid prefix teiid_infinispan, teiid_ is reserved for Teiid use.
{code}
I also noticed that name of properties are *teiid_infinispan-hotrod* but should be *teiid_ispn*.
Generated model in xml vdb:
{code:java}
SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2017' AS teiid_infinispan-hotrod
CREATE FOREIGN TABLE viewBooks (
isbn string(255) NOT NULL,
title string(255),
publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
type string(255),
CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
) OPTIONS(UPDATABLE 'TRUE', "teiid_infinispan-hotrod:CACHE" 'books_indexed');
CREATE FOREIGN TABLE ST_viewBooks (
isbn string(255) NOT NULL,
title string(255),
publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
type string(255),
CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
) OPTIONS(UPDATABLE 'TRUE', "teiid_infinispan-hotrod:CACHE" 'books_indexed_st');
{code}
Right model (in my opinion):
{code:java}
SET NAMESPACE 'http://www.teiid.org/translator/infinispan/2017' AS teiid_ispn
CREATE FOREIGN TABLE viewBooks (
isbn string(255) NOT NULL,
title string(255),
publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
type string(255),
CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
) OPTIONS(UPDATABLE 'TRUE', "teiid_ispn:CACHE" 'books_indexed');
CREATE FOREIGN TABLE ST_viewBooks (
isbn string(255) NOT NULL,
title string(255),
publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
type string(255),
CONSTRAINT pk_book PRIMARY KEY(isbn) OPTIONS(NAMEINSOURCE 'BOOKS')
) OPTIONS(UPDATABLE 'TRUE', "teiid_ispn:CACHE" 'books_indexed_st');
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-3174:
-----------------------------------
Workaround Description:
# Set up and run server if you don't have any server (infinispan-hotrod MED will be imported)
# Right click on generated JDG source model and select Modeling -> Manage Model Extension Definition
# Click to Add... and select infinispan-hotrod
# click to ok and finish button (now, model has set extension and property infinispan-hotrod:CACHE is set)
was:
# Set up and run server if you don't have any server (infinispan-hotrod MED will be imported)
# Left-click on generated JDG source model and select Modeling -> Manage Model Extension Definition
# Click to Add... and select infinispan-hotrod
# click to ok and finish button (now, model has set extension and property infinispan-hotrod:CACHE is set)
> Infinispan-hotrod MXD is not set after JDG materialization wizard
> -----------------------------------------------------------------
>
> Key: TEIIDDES-3174
> URL: https://issues.jboss.org/browse/TEIIDDES-3174
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1.1
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.1.2
>
>
> When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard.
> I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod).
> After that, I see infinispan-hotrod:CACHE which I defined in the wizard.
> Typ of infinispan-hotrod is *imported* so I must have set up a server *before*.
> In my point of view, the designer should set MED for JDG7 source model automatically.
> My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available.
> When I generate source model for JDG6.6, MED is set correctly (because MED is built-in).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months