[teiid-issues] [JBoss JIRA] (TEIID-3074) NPE When using External Materialization management is use

Steven Hawkins (JIRA) issues at jboss.org
Mon Aug 18 15:01:31 EDT 2014


    [ https://issues.jboss.org/browse/TEIID-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993686#comment-12993686 ] 

Steven Hawkins commented on TEIID-3074:
---------------------------------------

Consumes the threads?  That sounds even stranger.  At worst you'd expect the threads to be released after the exception.  It can 

> It looked like it was trying to execute "MVStatus" procedure for each row

With the function being defined as nondeterministic that is expected.  It should be command deterministic - but that may need refined if it appears multiple times in the same plan in the same form, such that it still does need to evaluate multiple times as a guard.  This is probably the root of what you are seeing, can you try changing the FunctionMethod function to be command deterministic instead?

So my guess is that a non-deterministic subquery that blocks will have the prior execution closed before it can return a value.

> NPE When using External Materialization management is use
> ---------------------------------------------------------
>
>                 Key: TEIID-3074
>                 URL: https://issues.jboss.org/browse/TEIID-3074
>             Project: Teiid
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Query Engine
>    Affects Versions: 8.5
>            Reporter: Ramesh Reddy
>            Assignee: Steven Hawkins
>         Attachments: debug_plan.txt, solr-integration-with-matview-vdb.xml
>
>
> When I was issuing query that has externalized materialization with management option to true, I am seeing NPE. Tried to see why NPE is occurring was not able to figure out (yet) 
> {code}
> 14:37:50,269 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8477) 0z97J5OWq7x9 Connector worker process failed for atomic-request=0z97J5OWq7x9.7.1.4220: java.lang.NullPointerException
> 	at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:338)
> 	at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:385) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> 	at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:203) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> 	at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> 	at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> 	at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> 	at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> 	at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> 	at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> 	at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> 	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the teiid-issues mailing list