[JBoss JIRA] (TEIID-4283) External Materialization interleaving loads SYSADMIN.loadMatView
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-4283?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-4283:
------------------------------------
I can also confirm, that when the "teiid_rel:MATVIEW_LOAD_SCRIPT" option is not specified and instead "teiid_rel:MATERIALIZED_STAGE_TABLE" is specified, the issue remains the same. The altered view definition:
{code:sql}
CREATE VIEW external_long_ttl (
customer_id integer NOT NULL,
total_amount integer
) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'FALSE',
MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view',
"teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
"teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable',
"teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
"teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
"teiid_rel:MATERIALIZED_STAGE_TABLE" 'Source.JSTASTNY.dv_matviews_mat_view_stage',
"teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table ${db.table.prefix}dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
"teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_stage TO ${db.table.prefix}dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view TO ${db.table.prefix}dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_temp TO ${db.table.prefix}dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
"teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT',
"teiid_rel:MATVIEW_TTL" 20000)
AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;
{code}
> External Materialization interleaving loads SYSADMIN.loadMatView
> ----------------------------------------------------------------
>
> Key: TEIID-4283
> URL: https://issues.jboss.org/browse/TEIID-4283
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.5
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Blocker
> Attachments: jdg-log.txt
>
>
> There is a possibility of two concurrent loads of single materialized view when using SYSADMIN.loadMatView function. I observed the issue while:
> # Waiting for ttl-driven reload and in right time I triggered another load explicitly by invoking the loadMatView function.
> # Invoking SYSADMIN.loadMatView function multiple times in quick succession.
> The view definition:
> {code:sql}
> CREATE VIEW external_long_ttl (
> customer_id integer NOT NULL,
> total_amount integer
> ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'FALSE',
> MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable',
> "teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;',
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table ${db.table.prefix}dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_stage TO ${db.table.prefix}dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view TO ${db.table.prefix}dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_temp TO ${db.table.prefix}dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT',
> "teiid_rel:MATVIEW_TTL" 20000)
> AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;
> {code}
> Query to explicitly load the view:
> {code:sql}
> exec SYSADMIN.loadMatView(schemaName=>'View',viewname=>'external_long_ttl', invalidate=>'true')
> {code}
> I attached a log which starts with ttl-driven load, then the explicit load is performed. The issue noticed is in teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT , where primary and staging tables are being swapped. The second load (explicit) can't find the original table, as the ttl-driven load had already renamed it.
> But this situation of two concurrent loads should never occur.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-4285) TEIID30019 Unexpected exception for request ... java.lang.AssertionError: Batch not found in storage
by Steve Tran (JIRA)
Steve Tran created TEIID-4285:
---------------------------------
Summary: TEIID30019 Unexpected exception for request ... java.lang.AssertionError: Batch not found in storage
Key: TEIID-4285
URL: https://issues.jboss.org/browse/TEIID-4285
Project: Teiid
Issue Type: Bug
Affects Versions: 8.12.x
Reporter: Steve Tran
Assignee: Steven Hawkins
My VDB stopped accepting ODBC-based connections. I wasn't able to identify the root cause, but I've gathered some facts.
- JDBC connections still worked
- ODBC connections to other VDBs worked fine
- Reloading via web-console of this particular VDB restored functionality
- Here's the stack trace
{code}
[Server:cdtssoa126d-jdv-one] 10:06:23,830 ERROR [org.teiid.PROCESSOR] (Worker2055_QueryProcessorQueue3763648) TEIID30019 Unexpected exception for request Z/WnBvmBk+w1.2: java.lang.AssertionError: Batch not found in storage 16855
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.impl.BufferManagerImpl$BatchManagerImpl.getBatch(BufferManagerImpl.java:306) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.SPage.getValues(SPage.java:237) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.SPage.search(SPage.java:139) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.STree.find(STree.java:246) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.TupleBrowser.setPage(TupleBrowser.java:146) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.TupleBrowser.nextTuple(TupleBrowser.java:210) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.tempdata.TempTable$QueryTupleSource.nextTuple(TempTable.java:192) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.tempdata.TempTableDataManager$ProxyTupleSource.nextTuple(TempTableDataManager.java:110) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:444) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:326) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:295) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at sun.reflect.GeneratedMethodAccessor144.invoke(Unknown Source) [:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at org.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:121) [teiid-api-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.jboss.TransportService$2.invoke(TransportService.java:226) [teiid-jboss-integration-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at com.sun.proxy.$Proxy135.executeRequest(Unknown Source)
[Server:cdtssoa126d-jdv-one] at sun.reflect.GeneratedMethodAccessor144.invoke(Unknown Source) [:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:174) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:258) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:172) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at com.sun.proxy.$Proxy135.executeRequest(Unknown Source)
[Server:cdtssoa126d-jdv-one] at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:634) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:509) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.odbc.ODBCServerRemoteImpl.getPgColInfo(ODBCServerRemoteImpl.java:1099) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.odbc.ODBCServerRemoteImpl.access$100(ODBCServerRemoteImpl.java:80) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.odbc.ODBCServerRemoteImpl$4.onCompletion(ODBCServerRemoteImpl.java:455) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:516) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.sendResultsIfNeeded(RequestWorkItem.java:920) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:646) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:218) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:189) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:444) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:326) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one]
[Server:cdtssoa126d-jdv-one] 10:06:24,246 ERROR [org.teiid.PROCESSOR] (Worker2055_QueryProcessorQueue3763650) TEIID30019 Unexpected exception for request Z/WnBvmBk+w1.4: java.lang.AssertionError: Batch not found in storage 11173
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.impl.BufferManagerImpl$BatchManagerImpl.getBatch(BufferManagerImpl.java:306) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.SPage.getValues(SPage.java:237) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.TupleBrowser.nextTuple(TupleBrowser.java:223) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.tempdata.TempTable$QueryTupleSource.nextTuple(TempTable.java:192) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.tempdata.TempTableDataManager$ProxyTupleSource.nextTuple(TempTableDataManager.java:110) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.SourceState.getTupleBuffer(SourceState.java:243) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.loadLeft(EnhancedSortMergeJoinStrategy.java:229) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:187) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:69) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:70) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:84) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.AbstractTupleSource.nextTuple(AbstractTupleSource.java:48) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.process(EnhancedSortMergeJoinStrategy.java:383) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:211) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.SourceState.getTupleBuffer(SourceState.java:243) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.loadLeft(EnhancedSortMergeJoinStrategy.java:229) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:187) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.SourceState.getTupleBuffer(SourceState.java:243) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.loadLeft(EnhancedSortMergeJoinStrategy.java:229) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:187) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:69) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:70) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:84) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.AbstractTupleSource.nextTuple(AbstractTupleSource.java:48) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.SortUtility.initialSort(SortUtility.java:269) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.SortUtility.sort(SortUtility.java:202) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.SortNode.sortPhase(SortNode.java:112) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.SortNode.getBuffer(SortNode.java:208) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.RelationalPlan.getBuffer(RelationalPlan.java:250) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.QueryProcessor.getBuffer(QueryProcessor.java:289) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:149) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:444) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:326) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one]
[Server:cdtssoa126d-jdv-one] 10:06:24,467 ERROR [org.teiid.PROCESSOR] (New I/O worker #17) TEIID30019 Unexpected exception for request Z/WnBvmBk+w1.5: java.lang.AssertionError: Batch not found in storage 14803
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.impl.BufferManagerImpl$BatchManagerImpl.getBatch(BufferManagerImpl.java:306) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.SPage.getValues(SPage.java:237) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.SPage.search(SPage.java:139) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.STree.find(STree.java:246) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.TupleBrowser.setPage(TupleBrowser.java:146) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.common.buffer.TupleBrowser.nextTuple(TupleBrowser.java:210) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.tempdata.TempTable$QueryTupleSource.nextTuple(TempTable.java:192) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.tempdata.TempTableDataManager$ProxyTupleSource.nextTuple(TempTableDataManager.java:110) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:444) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:326) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:295) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at sun.reflect.GeneratedMethodAccessor144.invoke(Unknown Source) [:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at org.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:121) [teiid-api-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.jboss.TransportService$2.invoke(TransportService.java:226) [teiid-jboss-integration-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at com.sun.proxy.$Proxy135.executeRequest(Unknown Source)
[Server:cdtssoa126d-jdv-one] at sun.reflect.GeneratedMethodAccessor144.invoke(Unknown Source) [:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:174) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:258) [teiid-engine-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:172) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at com.sun.proxy.$Proxy135.executeRequest(Unknown Source)
[Server:cdtssoa126d-jdv-one] at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:634) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:509) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261) [teiid-client-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.odbc.ODBCServerRemoteImpl.getPgColInfo(ODBCServerRemoteImpl.java:1099) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.odbc.ODBCServerRemoteImpl.prepare(ODBCServerRemoteImpl.java:502) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at sun.reflect.GeneratedMethodAccessor179.invoke(Unknown Source) [:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211) [teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:328) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
[Server:cdtssoa126d-jdv-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
[Server:cdtssoa126d-jdv-one]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-4283) External Materialization interleaving loads SYSADMIN.loadMatView
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-4283?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-4283:
------------------------------------
[~shawkins] I made an error when naming the log. This issue is not jdg-specific. I observed it on SAP HANA.
> External Materialization interleaving loads SYSADMIN.loadMatView
> ----------------------------------------------------------------
>
> Key: TEIID-4283
> URL: https://issues.jboss.org/browse/TEIID-4283
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.5
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Blocker
> Attachments: jdg-log.txt
>
>
> There is a possibility of two concurrent loads of single materialized view when using SYSADMIN.loadMatView function. I observed the issue while:
> # Waiting for ttl-driven reload and in right time I triggered another load explicitly by invoking the loadMatView function.
> # Invoking SYSADMIN.loadMatView function multiple times in quick succession.
> The view definition:
> {code:sql}
> CREATE VIEW external_long_ttl (
> customer_id integer NOT NULL,
> total_amount integer
> ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'FALSE',
> MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable',
> "teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;',
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table ${db.table.prefix}dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_stage TO ${db.table.prefix}dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view TO ${db.table.prefix}dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_temp TO ${db.table.prefix}dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT',
> "teiid_rel:MATVIEW_TTL" 20000)
> AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;
> {code}
> Query to explicitly load the view:
> {code:sql}
> exec SYSADMIN.loadMatView(schemaName=>'View',viewname=>'external_long_ttl', invalidate=>'true')
> {code}
> I attached a log which starts with ttl-driven load, then the explicit load is performed. The issue noticed is in teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT , where primary and staging tables are being swapped. The second load (explicit) can't find the original table, as the ttl-driven load had already renamed it.
> But this situation of two concurrent loads should never occur.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-4283) External Materialization interleaving loads SYSADMIN.loadMatView
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4283?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4283:
---------------------------------------
I'll see if I can confirm this. The load script should ensure the load is exclusive. If that is the case, then this is a JDG specific issue.
> External Materialization interleaving loads SYSADMIN.loadMatView
> ----------------------------------------------------------------
>
> Key: TEIID-4283
> URL: https://issues.jboss.org/browse/TEIID-4283
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.5
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Blocker
> Attachments: jdg-log.txt
>
>
> There is a possibility of two concurrent loads of single materialized view when using SYSADMIN.loadMatView function. I observed the issue while:
> # Waiting for ttl-driven reload and in right time I triggered another load explicitly by invoking the loadMatView function.
> # Invoking SYSADMIN.loadMatView function multiple times in quick succession.
> The view definition:
> {code:sql}
> CREATE VIEW external_long_ttl (
> customer_id integer NOT NULL,
> total_amount integer
> ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'FALSE',
> MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable',
> "teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;',
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table ${db.table.prefix}dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_stage TO ${db.table.prefix}dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view TO ${db.table.prefix}dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_temp TO ${db.table.prefix}dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT',
> "teiid_rel:MATVIEW_TTL" 20000)
> AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;
> {code}
> Query to explicitly load the view:
> {code:sql}
> exec SYSADMIN.loadMatView(schemaName=>'View',viewname=>'external_long_ttl', invalidate=>'true')
> {code}
> I attached a log which starts with ttl-driven load, then the explicit load is performed. The issue noticed is in teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT , where primary and staging tables are being swapped. The second load (explicit) can't find the original table, as the ttl-driven load had already renamed it.
> But this situation of two concurrent loads should never occur.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-3617) Provide an option to Limit per user based connections
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3617:
-------------------------------------
+1 for vdb based configuration. I suggest, something like
<vdb name="foo">
<property name="limit-connections/UserA" value="10"/>
<property name="limit-connections/UserB" value="15"/>
<property name="limit-connections/UserC" value="25"/>
</vdb>
> Provide an option to Limit per user based connections
> -----------------------------------------------------
>
> Key: TEIID-3617
> URL: https://issues.jboss.org/browse/TEIID-3617
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Xian Liu
> Assignee: Kylin Soong
> Fix For: 9.1
>
>
> we deploy teiid for users to get data, but some users will create many connections to teiid and they are not necessary, I need to find a good way to limit each user account can only get like 50 connections or so
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-3617) Provide an option to Limit per user based connections
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3617:
-------------------------------------
Since Teiid does not have sessions scoped at system level, it seems verbose to include the configuration to be at system level. There are also couple different issues when defining at system level.
1. The configuration needs to include per vdb and user. As user count is kept only at VDB scoped.
2. The security domain is unknown to the system, thus name of the user needs to be fully scoped as "user@teiid-security" thus complicating the issue. If the user changes the security-domain at VDB level, the setting in the system will be out of date.
So, it is recommended that to put this configuration at vdb level in the vdb.xml file, then the configuration is scoped to the VDB. This will resolve above two issues. However
1. The issue here is with the updatability of configuration at runtime. Currently there is limited support to update vdb.xml like we do in the change "connection-type", but the issue raised here is about migration. However, the migration can be looked as orthogonal issue, as we have that in either case to resolve.
> Provide an option to Limit per user based connections
> -----------------------------------------------------
>
> Key: TEIID-3617
> URL: https://issues.jboss.org/browse/TEIID-3617
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Xian Liu
> Assignee: Kylin Soong
> Fix For: 9.1
>
>
> we deploy teiid for users to get data, but some users will create many connections to teiid and they are not necessary, I need to find a good way to limit each user account can only get like 50 connections or so
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-3617) Provide an option to Limit per user based connections
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3617:
---------------------------------------
Since a user's identity is vdb / security-domain dependent there isn't a simple notion of identity at a system level. You'd have to have id's that are qualified by the security domain - user@domain and/or specify the vdb/version. Also configuration down to a transport level may considered optional - that is since there is now just a single session service, it doesn't need to be specific to jdbc/pg/etc.
Having this as part of the vdb / vdb.xml is better encapsulated, but makes it much more difficult to manage. We do have logic that allows for updates to the deployed vdb.xml, like the connection-type property, but there's currently no good way to export that I'm aware of. At worst we could just expect someone to add restrictions to the vdb.xml and redeploy.
Let's determine if it makes sense to have this at a vdb level (either specified as part of the system level restriction, or in the vdb.xml) and what that would imply in terms of management.
> Provide an option to Limit per user based connections
> -----------------------------------------------------
>
> Key: TEIID-3617
> URL: https://issues.jboss.org/browse/TEIID-3617
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Xian Liu
> Assignee: Kylin Soong
> Fix For: 9.1
>
>
> we deploy teiid for users to get data, but some users will create many connections to teiid and they are not necessary, I need to find a good way to limit each user account can only get like 50 connections or so
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (TEIID-4283) External Materialization interleaving loads SYSADMIN.loadMatView
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4283?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4283:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1348466
Bugzilla Update: Perform
> External Materialization interleaving loads SYSADMIN.loadMatView
> ----------------------------------------------------------------
>
> Key: TEIID-4283
> URL: https://issues.jboss.org/browse/TEIID-4283
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.5
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Blocker
> Attachments: jdg-log.txt
>
>
> There is a possibility of two concurrent loads of single materialized view when using SYSADMIN.loadMatView function. I observed the issue while:
> # Waiting for ttl-driven reload and in right time I triggered another load explicitly by invoking the loadMatView function.
> # Invoking SYSADMIN.loadMatView function multiple times in quick succession.
> The view definition:
> {code:sql}
> CREATE VIEW external_long_ttl (
> customer_id integer NOT NULL,
> total_amount integer
> ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'FALSE',
> MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable',
> "teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;',
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table ${db.table.prefix}dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_stage TO ${db.table.prefix}dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view TO ${db.table.prefix}dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_temp TO ${db.table.prefix}dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT',
> "teiid_rel:MATVIEW_TTL" 20000)
> AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;
> {code}
> Query to explicitly load the view:
> {code:sql}
> exec SYSADMIN.loadMatView(schemaName=>'View',viewname=>'external_long_ttl', invalidate=>'true')
> {code}
> I attached a log which starts with ttl-driven load, then the explicit load is performed. The issue noticed is in teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT , where primary and staging tables are being swapped. The second load (explicit) can't find the original table, as the ttl-driven load had already renamed it.
> But this situation of two concurrent loads should never occur.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months