[JBoss JIRA] (TEIID-2350) NPE during call generated REST service from browser
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2350?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2350.
---------------------------------
> NPE during call generated REST service from browser
> ---------------------------------------------------
>
> Key: TEIID-2350
> URL: https://issues.jboss.org/browse/TEIID-2350
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.2
> Environment: Windows 7, JBoss AS 7.1.1 Final
> Reporter: Vadim Melnikov
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> See also discussion at https://community.jboss.org/thread/219690
> Teiid 8.2
> Example from https://docs.jboss.org/author/display/teiid82final/REST+Service+Through+VDB
>
> {code:xml}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="sample" version="1">
>
> <property name="UseConnectorMetadata" value="true" />
> <property name="{http://teiid.org/rest}auto-generate" value="true"/>
> <property name="{http://teiid.org/rest}security-type" value="HttpBasic"/>
> <property name="{http://teiid.org/rest}security-domain" value="teiid-security"/>
> <property name="{http://teiid.org/rest}security-role" value="example-role"/>
> <property name="{http://teiid.org/rest}passthrough-auth" value="true"/>
>
> <model name="PM1">
> <source name="text-connector" translator-name="loopback" />
> <metadata type="DDL"><![CDATA[
> CREATE FOREIGN TABLE G1 (e1 string, e2 integer);
> CREATE FOREIGN TABLE G2 (e1 string, e2 integer);
> ]]> </metadata>
> </model>
> <model name="View" type ="VIRTUAL">
> <metadata type="DDL"><![CDATA[
> SET NAMESPACE 'http://teiid.org/rest' AS REST;
> CREATE VIRTUAL PROCEDURE g1Table(IN p1 integer) RETURNS TABLE (xml_out xml) OPTIONS (UPDATECOUNT 0, "REST:METHOD" 'GET', "REST:URI" 'g1/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME "rows", XMLATTRIBUTES (g1Table.p1 as p1), XMLAGG(XMLELEMENT(NAME "row", XMLFOREST(e1, e2)))) AS xml_out FROM PM1.G1;
> END
> ]]> </metadata>
> </model>
>
> </vdb>
> {code}
>
> Open URL: http://localhost:8080/sample_1/view/g1/1
> Error log was generated:
>
> org.jboss.resteasy.spi.UnhandledException: java.lang.NullPointerException
> org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:340)
> org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:214)
> org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:190)
> org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:540)
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> root cause
> java.lang.NullPointerException
> org.teiid.jboss.rest.TeiidRSProvider.execute(TeiidRSProvider.java:64)
> org.teiid.jboss.rest.View.g1Tableapplication_xml(Unknown Source)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:597)
> org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:155)
> org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:257)
> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:222)
> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:211)
> org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:525)
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (TEIID-2565) Problem with DDL returned via admin api - column has erroneous datatype
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2565?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2565.
---------------------------------
> Problem with DDL returned via admin api - column has erroneous datatype
> -----------------------------------------------------------------------
>
> Key: TEIID-2565
> URL: https://issues.jboss.org/browse/TEIID-2565
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 8.4
> Reporter: Mark Drilling
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> Deployed a greenplum datasource, then deployed a dynamic vdb and did a getSchema via the admin api. One of the tables in the ddl contains a column as shown in the following ddl snippet:
> CREATE FOREIGN TABLE "gp_toolkit.gp_log_command_timings" (
> logduration object(49) OPTIONS (NAMEINSOURCE '"logduration"', NATIVE_TYPE 'interval')
> ) OPTIONS (NAMEINSOURCE '"gp_toolkit"."gp_log_command_timings"', UPDATABLE TRUE);
> The logduration type of object erroneously has a length.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (TEIID-2502) Oracle Struct Serialization Error
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2502?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2502.
---------------------------------
> Oracle Struct Serialization Error
> ---------------------------------
>
> Key: TEIID-2502
> URL: https://issues.jboss.org/browse/TEIID-2502
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.2
> Environment: centos 6.3
> Reporter: luca gioppo
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
> Attachments: ora.patch
>
>
> I'm issuing a query (a simple select * from table) on a VDB's table that contains a geometric column from oracle spatial.
> I'm getting the following error in SquirrelSQL
> Error: org.teiid.net.socket.SingleInstanceCommunicationException
> SQLState: 08S01
> ErrorCode: 0
> Afterwards the connection is broken and I cannot access any other table and have to reconnect since I get:
> Error: Error Code:TEIID20013 Message:Error Code:TEIID20013 Message:java.net.SocketException: Socket closed
> SQLState: TEIID20013
> ErrorCode: 0
> I'm trying to access a SDO table and a geometry type column, but hoped that TEIID could read it as a BLOB without caring about the real type.
> Probably it doesn't like it too much.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (TEIID-2460) Weird behavior when Max buffer space restriction is hit
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2460?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2460.
---------------------------------
> Weird behavior when Max buffer space restriction is hit
> --------------------------------------------------------
>
> Key: TEIID-2460
> URL: https://issues.jboss.org/browse/TEIID-2460
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.6
> Reporter: Filip Nguyen
> Assignee: Steven Hawkins
> Fix For: 8.4, 7.7.7
>
> Attachments: teiid-jboss-beans.xml
>
>
> I was trying to restrict the disk space used by buffer manager (see steps to reproduce for my methodology). When the disk limit is hit, it really tries to stop the query, but doesn't succeed immediately.
> There is a big amount of exceptions [1] for relatively long period of time (minutes for big files), until it fails eventually with [2]. The error [2] is also given back to the JDBC client.
> Problem is that after the query fails in this fashion, the whole buffer disk space is still occupied and any new query, that needs even small (acceptable) buffer disk space, fails.
> Only way that I have found to make the buffer space usable again is to restart the server.
> [1] Error transferring block to storage 149742
> java.io.IOException: Max buffer space of 31,457,280 bytes has been exceed. The current operation will be aborted.
> [2] org.teiid.jdbc.TeiidSQLException: Batch not found in storage 50937
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months