[JBoss JIRA] (TEIID-4741) After VDB undeploy (due to VDB syntax errors), system throws several TeiidProcessingException Warnings
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4741?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-4741:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> After VDB undeploy (due to VDB syntax errors), system throws several TeiidProcessingException Warnings
> ------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4741
> URL: https://issues.jboss.org/browse/TEIID-4741
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Environment: * Teiid 9.1.2
> * WildFly 10
> Reporter: Pedro Inácio
> Assignee: Ramesh Reddy
> Fix For: 9.2
>
> Attachments: server.log
>
>
> After re-deploying a *VDB *(with a syntax errors this time), the system throws several warnings (until the server is stopped) related to the undeployed VDB.
> The errors are of type:
> _Caused by: org.teiid.core.TeiidProcessingException: TEIID31099 VDB ..._
> This should not be happening, since the VDB was undeployed.
> To be notice that the VDB has External Materialization.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4741) After VDB undeploy (due to VDB syntax errors), system throws several TeiidProcessingException Warnings
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4741?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-4741:
--------------------------------
Fix Version/s: 9.2
(was: 9.1.2)
> After VDB undeploy (due to VDB syntax errors), system throws several TeiidProcessingException Warnings
> ------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4741
> URL: https://issues.jboss.org/browse/TEIID-4741
> Project: Teiid
> Issue Type: Bug
> Components: Common
> Environment: * Teiid 9.1.2
> * WildFly 10
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Fix For: 9.2
>
> Attachments: server.log
>
>
> After re-deploying a *VDB *(with a syntax errors this time), the system throws several warnings (until the server is stopped) related to the undeployed VDB.
> The errors are of type:
> _Caused by: org.teiid.core.TeiidProcessingException: TEIID31099 VDB ..._
> This should not be happening, since the VDB was undeployed.
> To be notice that the VDB has External Materialization.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4741) After VDB undeploy (due to VDB syntax errors), system throws several TeiidProcessingException Warnings
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4741?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-4741:
--------------------------------
Component/s: Server
(was: Common)
> After VDB undeploy (due to VDB syntax errors), system throws several TeiidProcessingException Warnings
> ------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4741
> URL: https://issues.jboss.org/browse/TEIID-4741
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Environment: * Teiid 9.1.2
> * WildFly 10
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Fix For: 9.2
>
> Attachments: server.log
>
>
> After re-deploying a *VDB *(with a syntax errors this time), the system throws several warnings (until the server is stopped) related to the undeployed VDB.
> The errors are of type:
> _Caused by: org.teiid.core.TeiidProcessingException: TEIID31099 VDB ..._
> This should not be happening, since the VDB was undeployed.
> To be notice that the VDB has External Materialization.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4741) After VDB undeploy (due to VDB syntax errors), system throws several TeiidProcessingException Warnings
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4741?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4741:
-------------------------------------
I think at the time of re-deploy the scheduler is already had a job submitted based on the previous VDB, thus may be errors. We can do a check for VDB status before the materialization job is started.
> After VDB undeploy (due to VDB syntax errors), system throws several TeiidProcessingException Warnings
> ------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4741
> URL: https://issues.jboss.org/browse/TEIID-4741
> Project: Teiid
> Issue Type: Bug
> Components: Common
> Environment: * Teiid 9.1.2
> * WildFly 10
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Fix For: 9.1.2
>
> Attachments: server.log
>
>
> After re-deploying a *VDB *(with a syntax errors this time), the system throws several warnings (until the server is stopped) related to the undeployed VDB.
> The errors are of type:
> _Caused by: org.teiid.core.TeiidProcessingException: TEIID31099 VDB ..._
> This should not be happening, since the VDB was undeployed.
> To be notice that the VDB has External Materialization.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4743) Dependent View with External Materialization load problems
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4743?page=com.atlassian.jira.plugin... ]
Work on TEIID-4743 started by Steven Hawkins.
---------------------------------------------
> Dependent View with External Materialization load problems
> ----------------------------------------------------------
>
> Key: TEIID-4743
> URL: https://issues.jboss.org/browse/TEIID-4743
> Project: Teiid
> Issue Type: Bug
> Components: Common
> Environment: # MySql 5.6.35
> # WildFly 10
> # Teiid Server 9.1.2
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Fix For: 9.1.2
>
> Attachments: ddl.sql, externalMaterializationOrderProblem-vdb.xml, numberingPlan-vdb.xml
>
>
> Having defined two views with external materialization, and second view (my_view) uses the first view (numbering_plan).
> {panel:title=Second view (my_view) definition}
> CREATE VIEW my_view(
> ...
> )
> OPTIONS(
> MATERIALIZED 'TRUE',
> MATERIALIZED_TABLE 'MyMaterialized.my_view_cache',
> ....
> )
> AS
> SELECT cns,
> country_code
> FROM NumberingPlan2.numbering_plan;
> {panel}
> When _my_view_ is loaded for the first time the following error appears:
> {panel:title=First Warning}
> 14:41:13,693 WARN [org.teiid.MATVIEWS] (Worker1_QueryProcessorQueue27) 7qmYa3eWflIY org.teiid.jdbc.TeiidSQLException: TEIID30328 Unable to evaluate (SELECT mvstatus('NumberingPlan2', 'numbering_plan', Valid, LoadState, 'THROW_EXCEPTION') FROM (SELECT 1) AS x LEFT OUTER JOIN NumberingPlanMaterialized2.status ON SchemaName = 'NumberingPlan2' AND Name = 'numbering_plan' LIMIT 2): TEIID30328 Unable to evaluate mvstatus('NumberingPlan2', 'numbering_plan', Valid, LoadState, 'THROW_EXCEPTION'): TEIID30384 Error while evaluating function mvstatus
> {panel}
> If _my_view _is queried in the meantime something like this appears in logs (and in the client who tried to perform the query against _my_view_):
> {panel:title=Invoking my_view error}
> 14:49:04,493 WARN [org.teiid.PROCESSOR] (Worker7_QueryProcessorQueue10979) 57KCZOf/UjCV TEIID30020 Processing exception for request 57KCZOf/UjCV.0 'Group does not exist: my_view'. Originally QueryResolverException ResolverUtil.java:880. Enable more detailed logging to see the entire stacktrace.
> {panel}
> We have to wait until _my_view_ *MATVIEW_TTL* 'expires' in order for the view to be loaded and start to have results being returned. Of course we can call *loadMatView *explicitly, but the system could be wise enough to know that has one view that is dependent of another and that the materialization must occur first, so it should have waited in the background for the _numbering_plan _materialization to occur and then trigger the materialization of _my_view_ afterwards (or if the materialization is not available then at least consult the 'original' data instead).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4744) Prior execution is not being closed in transactional secenario
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4744?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4744.
-----------------------------------
Fix Version/s: 9.2
Resolution: Done
Calling close in the serial case more quickly.
> Prior execution is not being closed in transactional secenario
> --------------------------------------------------------------
>
> Key: TEIID-4744
> URL: https://issues.jboss.org/browse/TEIID-4744
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> When working in transactional scenario, where all the queries in plan are executed serially in a given thread, however, JDBC drivers like Netezza do not allow to keep more than single statement open on a given connection.
> To work with this issue, Teiid provides a translator override called "ThreadBound" where it forces the previous statement to finish executing (it caches the results if needs to be) before it can execute the next source command on the same connection. It looks like Teiid is not closing the prior statement before it moves on to execute the next statement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4722) TEIID30019: java.lang.AssertionError: Assertion failed assertion due to guard against a corner condition.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4722?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4722:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1419137, https://bugzilla.redhat.com/show_bug.cgi?id=1416482 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1416482)
> TEIID30019: java.lang.AssertionError: Assertion failed assertion due to guard against a corner condition.
> -----------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4722
> URL: https://issues.jboss.org/browse/TEIID-4722
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7.10.6_2
> Reporter: Johnathon Lee
> Assignee: Steven Hawkins
> Fix For: 9.2, 9.1.3
>
>
> Assertion failure:
> {code:java}
> ERROR [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue19151) TEIID30019 Unexpected exception for request WrzxYIqVWQ8G.11: java.lang.AssertionError: Assertion failed.
> at org.teiid.core.util.Assertion.failed(Assertion.java:73) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.core.util.Assertion.assertTrue(Assertion.java:68) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.core.util.Assertion.assertTrue(Assertion.java:60) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.query.processor.relational.MergeJoinStrategy.setProcessingSortRight(MergeJoinStrategy.java:367) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.query.processor.relational.DependentAccessNode.prepareNextCommand(DependentAccessNode.java:162) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.query.processor.relational.AccessNode.openInternal(AccessNode.java:259) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:371) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4736) JDG resource adapter does not reconnect properly when JDG as mat cache is restarted
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4736?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4736:
----------------------------------
Fix Version/s: 9.2
> JDG resource adapter does not reconnect properly when JDG as mat cache is restarted
> -----------------------------------------------------------------------------------
>
> Key: TEIID-4736
> URL: https://issues.jboss.org/browse/TEIID-4736
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 8.12.x, 9.0.1
> Reporter: William DeCoste
> Assignee: Van Halbert
> Fix For: 9.2
>
>
> After JDG restart, JDV cannot recover:
> Executing using the TeiidDriver
> org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 PersonMatSource1: Program Error: Cache Name is null
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:721)
> at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:64)
> at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:560)
> at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135)
> at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40)
> at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79)
> at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:268)
> at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:306)
> 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.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:98)
> at com.sun.proxy.$Proxy24.read(Unknown Source)
> at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:405)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:569)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:1063)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:338)
> at JDBCClient.execute(JDBCClient.java:93)
> at JDBCClient.main(JDBCClient.java:48)
> 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.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:293)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.teiid.core.TeiidProcessingException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 PersonMatSource1: Program Error: Cache Name is null
> at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:401)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:161)
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ... 1 more
> Caused by: org.teiid.core.TeiidException: Remote org.teiid.translator.TranslatorException: Program Error: Cache Name is null
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleError(ConnectorWorkItem.java:310)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:369)
> at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source)
> 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:211)
> at com.sun.proxy.$Proxy113.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> ... 6 more
> Caused by: java.lang.Error: Remote java.lang.AssertionError: Program Error: Cache Name is null
> at org.teiid.core.util.Assertion.failed(Assertion.java:73)
> at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100)
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanManagedConnectionFactory.getCache(InfinispanManagedConnectionFactory.java:173)
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.getCache(InfinispanConnectionImpl.java:251)
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.getQueryFactory(InfinispanConnectionImpl.java:140)
> at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.getQueryBuilder(DSLSearch.java:205)
> at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:156)
> at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:143)
> at org.teiid.translator.object.ObjectExecution.execute(ObjectExecution.java:261)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:366)
> ... 16 more
> -----------------------------------
> Executing using the TeiidDataSource
> org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 PersonMatSource1: Program Error: Cache Name is null
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:721)
> at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:64)
> at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:560)
> at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135)
> at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40)
> at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79)
> at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:268)
> at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:306)
> 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.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:98)
> at com.sun.proxy.$Proxy24.read(Unknown Source)
> at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:405)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:569)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:1063)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:338)
> at JDBCClient.execute(JDBCClient.java:93)
> at JDBCClient.main(JDBCClient.java:55)
> 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.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:293)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.teiid.core.TeiidProcessingException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 PersonMatSource1: Program Error: Cache Name is null
> at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:401)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:161)
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ... 1 more
> Caused by: org.teiid.core.TeiidException: Remote org.teiid.translator.TranslatorException: Program Error: Cache Name is null
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleError(ConnectorWorkItem.java:310)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:369)
> at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source)
> 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:211)
> at com.sun.proxy.$Proxy113.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> ... 6 more
> Caused by: java.lang.Error: Remote java.lang.AssertionError: Program Error: Cache Name is null
> at org.teiid.core.util.Assertion.failed(Assertion.java:73)
> at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100)
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanManagedConnectionFactory.getCache(InfinispanManagedConnectionFactory.java:173)
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.getCache(InfinispanConnectionImpl.java:251)
> at org.teiid.resource.adapter.infinispan.dsl.InfinispanConnectionImpl.getQueryFactory(InfinispanConnectionImpl.java:140)
> at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.getQueryBuilder(DSLSearch.java:205)
> at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:156)
> at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:143)
> at org.teiid.translator.object.ObjectExecution.execute(ObjectExecution.java:261)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:366)
> ... 16 more
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4744) Prior execution is not being closed in transactional secenario
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-4744:
-----------------------------------
Summary: Prior execution is not being closed in transactional secenario
Key: TEIID-4744
URL: https://issues.jboss.org/browse/TEIID-4744
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
When working in transactional scenario, where all the queries in plan are executed serially in a given thread, however, JDBC drivers like Netezza do not allow to keep more than single statement open on a given connection.
To work with this issue, Teiid provides a translator override called "ThreadBound" where it forces the previous statement to finish executing (it caches the results if needs to be) before it can execute the next source command on the same connection. It looks like Teiid is not closing the prior statement before it moves on to execute the next statement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months