[JBoss JIRA] (TEIID-2331) TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2331?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2331.
---------------------------------
> TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-2331
> URL: https://issues.jboss.org/browse/TEIID-2331
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.1
> Environment: Windows 7
> Reporter: Sabina Norderhaug
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 8.3
>
>
> We are getting this exception during continious execution. Looks like client cancelling the execution
> 16:13:16,171 ERROR [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue902) TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException
> at org.teiid.dqp.internal.process.RequestWorkItem.sendResultsIfNeeded(RequestWorkItem.java:753)
> at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:557)
> at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:191)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:166)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:219)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:249)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (TEIID-2394) Allow local connections to use thread bound transactions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2394?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2394.
---------------------------------
> Allow local connections to use thread bound transactions
> --------------------------------------------------------
>
> Key: TEIID-2394
> URL: https://issues.jboss.org/browse/TEIID-2394
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 7.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 8.3
>
>
> To facilitate usage of non-pooled local connections, it would be useful for the engine to automatically use the thread bound transaction for queries.
> An approximate workaround in local mode is to set the userSourceQueryConcurrency to 1 and use the disableLocalTxn property if needed to prevent calling code from starting a local transaction. The downside of this approach is that non-transactional work will be performed serially and Teiid temporary tables will not be transactionally aware.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (TEIID-2445) vdb.xml usability enhancements
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2445?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2445.
---------------------------------
> vdb.xml usability enhancements
> ------------------------------
>
> Key: TEIID-2445
> URL: https://issues.jboss.org/browse/TEIID-2445
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> Couple of usability enhancements need to be done on the -vdb.xml to make the intent clear
> UseConnectorMetadata=true/cached
> - The true case could be removed entirely. The notion of metadata caching could be handled by a model property and should probably be more baked into the MetadataRepository facility (such as passing the cached metadata in for update).
> supports-multi-source-bindings=true/false
> - Since we have mostly removed the binding terminology, it would make more sense to call this just multi-source or multisource (which is consistent with the multisource.columnName and addColumn properties). We could also automatically infer it to be true when there are multiple sources listed for a single model (which is currently an error case without this property) so that it would only be needed if you wanted a single source to appear as if it were a multisource model.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (TEIID-2427) Include nested message in processing exception warnings
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2427?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2427.
---------------------------------
> Include nested message in processing exception warnings
> -------------------------------------------------------
>
> Key: TEIID-2427
> URL: https://issues.jboss.org/browse/TEIID-2427
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> In many instances (especially with initial non-teiid exceptions) the original intent of the exception is not clear in the warning logged by teiid because only the top level message is there (for teiid exceptions we'll typically have the code chain, but that's not necessarily useful for the user). The root message would also be helpful so that detail logging is not needed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months