March 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5643) When querying a larger dataset, teiid answers with 504 Gateway Time-out and throws exception

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5643?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5643: --------------------------------------- Thanks Christoph, I'll have a look at this tomorrow. > When querying a larger dataset, teiid answers with 504 Gateway Time-out and throws exception > -------------------------------------------------------------------------------------------- > > Key: TEIID-5643 > URL: https://issues.jboss.org/browse/TEIID-5643 > Project: Teiid > Issue Type: Bug > Affects Versions: 11.2.1 > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Attachments: Heap Dump analysis tool.pdf, logfile2.txt, logfile3.txt > > > Please note, I am using Teiid 11.2.0 and not 11.2.1 as specified above in this ticket. I was not able to select a version 11.2.0. > The issue: I tried to query a table with a larger amount of records (about 600.000 records in the table). Teiid responds with > 504 Gateway Time-out. The server didn't respond in time. > If Teiid tries to respond with 600.000 entries to such a request, it is reasonable that it runs out of memory or other weird things happen. However, I would expect that in such a case Teiid just answers with a fixed amount of records, say for example 1000, and provides a kind of curser to enable subsequent requests to retrieve more data. > I am currently trying to find a workaround for the issue, as the issue blocks my work. Is there maybe a kind of configuration option that I have to set explicitly for such a kind of behavior I previously sketched? > Further note: When I send such a kind of select * request on the table to Teiid, I am also not able for a certain time interval, about a minute, to get a responds to different queries which select a single element on the mentioned table. Such a request then also results in a 504 Gateway Time-out. > Attached error log: > 2019-02-01 22:33:36,126 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Worker2_QueryProcessorQueue5) eayVFuq9y7OY IJ000407: No lazy enlistment available for my_nutri_diary > 2019-02-01 22:33:36,135 INFO [org.teiid.CONNECTOR] (Worker2_QueryProcessorQueue5) eayVFuq9y7OY MySQLExecutionFactory Commit=true;DatabaseProductName=MySQL;DatabaseProductVersion=8.0.13;DriverMajorVersion=8;DriverMajorVersion=0;DriverName=MySQL Connector/J;DriverVersion=mysql-connector-java-8.0.13 (Revision: 66459e9d39c8fd09767992bc592acd2053279be6);IsolationLevel=2 > 2019-02-01 22:36:56,959 WARN [org.teiid.CONNECTOR] (Worker2_QueryProcessorQueue5) eayVFuq9y7OY Connector worker process failed for atomic-request=eayVFuq9y7OY.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.`idCode` AS c_0, g_0.`lc` AS c_1, g_0.`product_name` AS c_2, g_0.`origins` AS c_3, g_0.`brands` AS c_4, g_0.`quantity` AS c_5, g_0.`nova_group` AS c_6, g_0.`nutrition_grade_fr` AS c_7, g_0.`ingredients_text_with_allergens` AS c_8, g_0.`energy_100g` AS c_9, g_0.`carbohydrates_100g` AS c_10, g_0.`sugars_100g` AS c_11, g_0.`proteins_100g` AS c_12, g_0.`fat_100g` AS c_13, g_0.`saturated_fat_100g` AS c_14, g_0.`saturated_fat_modifier` AS c_15, g_0.`salt_100g` AS c_16, g_0.`sodium_100g` AS c_17 FROM `FDBProducts` AS g_0 ORDER BY c_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:127) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:393) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:229) > at com.sun.proxy.$Proxy51.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:302) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:104) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:61) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:278) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.sql.SQLException: Java heap space > at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129) > at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97) > at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) > at com.mysql.cj.jdbc.ClientPreparedStatement.executeInternal(ClientPreparedStatement.java:974) > at com.mysql.cj.jdbc.ClientPreparedStatement.executeQuery(ClientPreparedStatement.java:1024) > at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:504) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:119) > ... 18 more > 2019-02-01 22:36:56,977 WARN [org.teiid.PROCESSOR] (default task-4) eayVFuq9y7OY TEIID30020 Processing exception for request eayVFuq9y7OY.0 'TEIID30504 my_nutri_diary: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.`idCode` AS c_0, g_0.`lc` AS c_1, g_0.`product_name` AS c_2, g_0.`origins` AS c_3, g_0.`brands` AS c_4, g_0.`quantity` AS c_5, g_0.`nova_group` AS c_6, g_0.`nutrition_grade_fr` AS c_7, g_0.`ingredients_text_with_allergens` AS c_8, g_0.`energy_100g` AS c_9, g_0.`carbohydrates_100g` AS c_10, g_0.`sugars_100g` AS c_11, g_0.`proteins_100g` AS c_12, g_0.`fat_100g` AS c_13, g_0.`saturated_fat_100g` AS c_14, g_0.`saturated_fat_modifier` AS c_15, g_0.`salt_100g` AS c_16, g_0.`sodium_100g` AS c_17 FROM `FDBProducts` AS g_0 ORDER BY c_0]'. Originally TeiidProcessingException 'Java heap space' SQLError.java:129. Enable more detailed logging to see the entire stacktrace. > 2019-02-01 22:36:56,987 WARN [org.teiid.PROCESSOR] (default task-4) TEIID16053 Unable to process odata request due to: TEIID30504 my_nutri_diary: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.`idCode` AS c_0, g_0.`lc` AS c_1, g_0.`product_name` AS c_2, g_0.`origins` AS c_3, g_0.`brands` AS c_4, g_0.`quantity` AS c_5, g_0.`nova_group` AS c_6, g_0.`nutrition_grade_fr` AS c_7, g_0.`ingredients_text_with_allergens` AS c_8, g_0.`energy_100g` AS c_9, g_0.`carbohydrates_100g` AS c_10, g_0.`sugars_100g` AS c_11, g_0.`proteins_100g` AS c_12, g_0.`fat_100g` AS c_13, g_0.`saturated_fat_100g` AS c_14, g_0.`saturated_fat_modifier` AS c_15, g_0.`salt_100g` AS c_16, g_0.`sodium_100g` AS c_17 FROM `FDBProducts` AS g_0 ORDER BY c_0] Increase the log level to see the entire stack trace. > 2019-02-01 22:36:57,213 WARN [org.teiid.CONNECTOR] (Worker2_QueryProcessorQueue6) NdaDihMR2Vlt Connector worker process failed for atomic-request=NdaDihMR2Vlt.0.0.1: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.`idCode` AS c_0, g_0.`lc` AS c_1, g_0.`product_name` AS c_2, g_0.`origins` AS c_3, g_0.`brands` AS c_4, g_0.`quantity` AS c_5, g_0.`nova_group` AS c_6, g_0.`nutrition_grade_fr` AS c_7, g_0.`ingredients_text_with_allergens` AS c_8, g_0.`energy_100g` AS c_9, g_0.`carbohydrates_100g` AS c_10, g_0.`sugars_100g` AS c_11, g_0.`proteins_100g` AS c_12, g_0.`fat_100g` AS c_13, g_0.`saturated_fat_100g` AS c_14, g_0.`saturated_fat_modifier` AS c_15, g_0.`salt_100g` AS c_16, g_0.`sodium_100g` AS c_17 FROM `FDBProducts` AS g_0 ORDER BY c_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:127) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:393) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:229) > at com.sun.proxy.$Proxy51.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:302) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:104) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:61) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:278) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5675) Fail, rather than ignore the apply option for OData

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5675?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5675. ----------------------------------- Resolution: Done Added an exception for apply and changed all of the sql builder not implemented exception handling to 501 status codes. > Fail, rather than ignore the apply option for OData > --------------------------------------------------- > > Key: TEIID-5675 > URL: https://issues.jboss.org/browse/TEIID-5675 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2, 12.1.1 > > > We are currently ignoring $apply - it should generate a not implemented exception instead. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3522) Provide Data Aggregation Extension to OData V4

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-3522?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3522: --------------------------------------- For 12.1+ TEIID-5675 will fail if apply is seen. There is also a minor olingo issue in that the url visitor did not have a visit method for the ApplyOption. I'll submit as issue for that. > Provide Data Aggregation Extension to OData V4 > ---------------------------------------------- > > Key: TEIID-3522 > URL: https://issues.jboss.org/browse/TEIID-3522 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > OData V4 specification defines extension for Data Aggregation http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs01/oda... > Teiid should provide support for this extension. There is Olingo support on this yet. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5675) Fail, rather than ignore the apply option for OData

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5675: ------------------------------------- Summary: Fail, rather than ignore the apply option for OData Key: TEIID-5675 URL: https://issues.jboss.org/browse/TEIID-5675 Project: Teiid Issue Type: Quality Risk Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.2, 12.1.1 We are currently ignoring $apply - it should generate a not implemented exception instead. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-52) Organize docs as much as possible into topics

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-52?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIIDSB-52: -------------------------------- Component/s: documentation > Organize docs as much as possible into topics > --------------------------------------------- > > Key: TEIIDSB-52 > URL: https://issues.jboss.org/browse/TEIIDSB-52 > Project: Teiid Spring Boot > Issue Type: Sub-task > Components: documentation > Reporter: Steven Hawkins > Priority: Major > > To align with product documentation the docs need to be as topic (a particular dev/admin action) based as possible - rather than general subject areas. We also need to update anything listing steps to use a numbered list with as granular as possible steps. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-57) Provide Cassandra data source support

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-57?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIIDSB-57: -------------------------------- Component/s: datasource > Provide Cassandra data source support > ------------------------------------- > > Key: TEIIDSB-57 > URL: https://issues.jboss.org/browse/TEIIDSB-57 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Priority: Major > > Provide data source support for Cassandra -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-48) Clean up README.md in teiid-openshift-examples

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-48?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-48. --------------------------------- Fix Version/s: 1.0.3 Resolution: Done > Clean up README.md in teiid-openshift-examples > ---------------------------------------------- > > Key: TEIIDSB-48 > URL: https://issues.jboss.org/browse/TEIIDSB-48 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Trivial > Fix For: 1.0.3 > > > The README.md needs to be cleaned up so that its easier to read on github. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-58) Provide data source support for LDAP

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-58: ----------------------------------- Summary: Provide data source support for LDAP Key: TEIIDSB-58 URL: https://issues.jboss.org/browse/TEIIDSB-58 Project: Teiid Spring Boot Issue Type: Feature Request Components: datasource Reporter: Ramesh Reddy Provide data source support for LDAP -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-57) Provide Cassandra data source support

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-57: ----------------------------------- Summary: Provide Cassandra data source support Key: TEIIDSB-57 URL: https://issues.jboss.org/browse/TEIIDSB-57 Project: Teiid Spring Boot Issue Type: Feature Request Reporter: Ramesh Reddy Provide data source support for Cassandra -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-56) Provide OData Source support

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-56: ----------------------------------- Summary: Provide OData Source support Key: TEIIDSB-56 URL: https://issues.jboss.org/browse/TEIIDSB-56 Project: Teiid Spring Boot Issue Type: Feature Request Components: datasource Reporter: Ramesh Reddy Provide the OData as source support. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2019